Categories
- All Categories
- 5 Oracle Analytics Sharing Center
- 11 Oracle Analytics Lounge
- 196 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.5K Oracle Analytics Forums
- 6K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 68 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Classic report with a DV dataset not working after migration due to ownership mismatch

Hi , We have an OAC classic report in FDI which uses a DV dataset (Created using DV connection to ADW Schema table) . This dataset was created by USER1If you read the session log , each column from the table is reference in the format .
XSA('USER1'.'DW_X_AR_ALTYX_CASHREPORT_V')."DW_X_ALTYX_CASHREPORT_V"."ACCOUNT_NO_TEXT"
Now for PROD migration , we need to depend on USER2 , since USER1 does not have access. USER2 has completed migration and now the report fails . Editing the report also not possible , it throws the error (Panel Div 'idReport' not found in document).The linked dataset already exists in PROD , but it was migrated earlier by USER3 who no longer existsWhat is the recommended approach to overcome this failure ?
How do i repoint the dataset in this report, considering that Edit report itself is failing ?
Answers
-
@Deepa Mohan - Kindly use content management to change the ownership.
Navigation - OAC Console > Content ManagementYou can change the ownership of Oracle Analytics content from the Console. For example, if an employee leaves your organization, you can reassign their workbooks and machine learning models to different employees so that they can use them.
Changing ownership enables you to reuse analytics content if the original content author is no longer in your organization. You can also quickly provide analytics users with access to analytics content.
Reference:
0 -
Hi Sumanth ,
Thank you for the response .
The question is not really about changing ownership of catalog objects. We have already tried this and it doesnt help.
There is an object ID associated to each DV dataset and it is in the form of USERNAME.DATASETNAME .
. It refers to this object ID every time a query is run and this object ID remains the same even upon changing the ownership of the object . This is the reason the report fails when opened in another environment after migration.
Thanks,Deepa
0 -
0