Page tree
Skip to end of metadata
Go to start of metadata
Description

The problem occurs in the General or Application Views.

 If you have a screenshot not showing the page you are in (you may see only the section), search in the Release documentation > User Guides which page contains this section.

After export and import of Oracle central data base, when trying to connect to the Dashboard with non administrator user: No graph and no data available as shown in following screenshot. 

Applicable in CAST Version
Release
Yes/No
8.3.x(question)
8.2.x(question)
8.1.x(question)
8.0.x(question)
7.3.x(question)
7.2.x(tick)
7.0.x(tick)
Action Plan

If you are in the FRAME_PORTAL_PORTFOLIO_VIEW, this issue could happen when a system is deleted, to encounter the issue, go to change portfolio and choose the good system.

The issue occurs because the oracle views associated to non administrator dashboard user are being invalid after the export and the import of the central data base.

Example:

Following the list of views associated for a giver non administrator dashboard user called USR_APPLI_1

  • USR_APPLI_1_DSS_OBJECTS_EX
  • USR_APPLI_1_DSS_METRIC_RESULTS
  • USR_APPLI_1_DSS_OBJECTS

In fact, the creation script of each one of these views is using the schema name of the user owner of the central base. If the import user is different from the export user, these views will be invalid after the import.

Example:

Here the creation script of the VIEW USR_APPLI_1_DSS_OBJECTS on the ‘CENTRAL_DEV’ database

create or replace Noforce VIEW USR_APPLI_1_DSS_OBJECTS

( OBJECT_ID, OBJECT_TYPE_ID, OBJECT_NAME, OBJECT_DESCRIPTION, OBJECT_FULL_NAME )

As

(Select  O.OBJECT_ID, O.OBJECT_TYPE_ID, O.OBJECT_NAME,  O.OBJECT_DESCRIPTION, O.OBJECT_FULL_NAME  from CENTRAL_DEV.DSS_OBJECTS O, CENTRAL_DEV.VIEWER_USER_ACCESS U where  O.OBJECT_ID=U.OBJECT_ID and U.USER_ID='BatchClient' and U.OBJECT_CATEGORY=1)

When exporting ‘CENTRAL_DEV’ to import it ‘CENTRAL_PROD’ schema for example, the view will be imported with compilation error. It will be invalid.

In this we can suggest 2 solutions

  1. Validate the views using an SQL tool
    1. Edit the creation script, replace the name of the original schema by the name of the import user ( Example: replace ‘CENTRAL_DEV’ by ‘CENTRAL_PROD’.
    2. Compile the views
  2. Recreate the non administrator user via the dashboard
    1. Connect to the dashboard with administrator user
    2. Access to user administration page ( via the Quick page)
    3. Remove the actual user and recreate it again In this case, the views will be recreated with the import user and will be valid.
Notes / Comments


Related Pages


  • No labels