“Failed to fetch data from DASHBOARD_FOLDERS “ error after ALM project(s) upgrade

Question ID: 110191
0
0

Hello,

  We have recently upgraded our ALM version and projects without issue. The verification maintenance routine reports all is fine and nothing to repair, therefor the repair routine does nothing. However, when we go into the various modules we get the following error when trying to view the details: “Failed to fetch data from DASHBOARD_FOLDERS”. Where should we be looking?

HomerJ

Marked as spam
Posted by (Questions: 366, Answers: 29)
Asked on July 31, 2021 9:57 am
8 views
Answers (1)
1
Private answer

Hello HomrJ,

 

I have seen the following suggested when trying to resolve this issue (as it has a long history of versions reporting it (it is rather generic and generally associated with the DB tables during an upgrade and not the specific version related errors we see lots of times. Here are my suggestions:
1) the root cause for this issue is usually related to the following views in DB for analysis view were not copied correctly to the project DB or they are missing (must be checked first in the Analysis Item folders)
VF_ANALYSIS_ITEM_FOLDERS
VF_ANALYSIS_ITEMS

In such situation verify and repair tool might be not able to fix the issue.

The manual Workaround if the verify does not fix this:
To fix this issue the user need to create or replace the view manually in new project DB. Use the following Query to create the missing view (make sure you have backups of everything prior to attempting any changes or fixes just in case):

CREATE OR REPLACE FORCE VIEW "<Schema/DB name >"."VF_ANALYSIS_ITEM_FOLDERS" ("VF_AIF_ID", "AIF_PUBLIC") AS SELECT ANALYSIS_ITEM_FOLDERS.AIF_ID AS VF_AIF_ID, ANALYSIS_SEGMENTS.AS_IS_PUBLIC AS AIF_PUBLIC FROM ANALYSIS_ITEM_FOLDERS INNER JOIN ANALYSIS_SEGMENTS ON ANALYSIS_ITEM_FOLDERS.AIF_SEGMENT_ID = ANALYSIS_SEGMENTS.AS_ID;

CREATE OR REPLACE FORCE VIEW "<Schema/DB name >"."VF_ANALYSIS_ITEMS" ("VF_AI_ID", "AI_PUBLIC") AS SELECT ANALYSIS_ITEMS.AI_ID AS VF_AI_ID, ANALYSIS_SEGMENTS.AS_IS_PUBLIC AS AI_PUBLIC FROM ANALYSIS_ITEMS INNER JOIN ANALYSIS_SEGMENTS ON ANALYSIS_ITEMS.AI_SEGMENT_ID = ANALYSIS_SEGMENTS.AS_ID;

2). Having said the above I have encountered this error before and it was related to the D transformation from Windows authentication (all tables using this are prefaced with “dbo.”) to SQL Authentication (all tables using this are prefaced with “td.”). In our case when we transformed these the views from the query in 1 were there already but hadn’t been changed from dbo. To td. When we accomplished this, the data became visible again.

Hope this helps,

Dan

Marked as spam
Posted by (Questions: 0, Answers: 761)
Answered on July 31, 2021 9:58 am