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.
Following the list of views associated for a giver non administrator dashboard user called USR_APPLI_1
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.
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 )
(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
- Validate the views using an SQL tool
- 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’.
- Compile the views
- Recreate the non administrator user via the dashboard
- Connect to the dashboard with administrator user
- Access to user administration page ( via the Quick page)
- Remove the actual user and recreate it again In this case, the views will be recreated with the import user and will be valid.