Clean Up and Reconfigure Your Semantic Model File (RPD)

You must reconfigure data source connection information and clean up your semantic model file (RPD) before you migrate content from Oracle Analytics Cloud to Oracle Analytics Server.

  • Reconfigure connections to your data.
  • Reconfigure connections to your usage tracking database (if required).
  • Remove objects you no longer need or don't want to migrate to Oracle Analytics Server.
  • Remove or disable objects that Oracle Analytics Server doesn’t support. If you haven't done so already, read Feature Availability and Comparison with Oracle Analytics Cloud.

To clean up an edit the semantic model file (RPD):

  1. Download and install the Oracle Analytics Client Tools version that matches the source Oracle Analytics Cloud (January 2022, 6.4).
  2. In Model Administration Tool, connect to Oracle Analytics Cloud. Click the File menu, select Open, then In the Cloud, and enter the connection information.
  3. Download the latest semantic model file locally.
    1. Click the File menu, then click Save As.
    2. Enter a suitable name for the file. For example, myoac_classic.rpd.
      The default password is the password you used to connect to Oracle Analytics Cloud.
    3. Click Yes to run a global consistency check.
    4. Save the file locally.
  4. In Model Administration Tool, open the semantic model file that you saved locally.
  5. Change the password, if required.
    Make a note of the password that you set for the semantic model file (RPD).
  6. Update database connection information.
    If you configured Data Gateway to enable access to your on-premise database or you moved your data to a different database you need to reconfigure your database connections.
    1. Navigate to the Physical Layer pane, select the database connection you want to edit, and open the Connection Pool dialog.
    2. Edit the connection details In Data Source Name.

    If your semantic model file includes connections to multiple databases, ensure that the settings for each connection pool are correct.

    If you configured a usage tracking database for Oracle Analytics Cloud and you want to use a different database for Oracle Analytics Server, update the connection pool settings.

  7. Delete unused database connections that you don't need anymore.
  8. Clean up initialization block information:
    1. Verify that initialization blocks point to the correct data source.
    2. Disable or delete unused initialization blocks that you don't need anymore.
  9. Review any semantic model or session variables.
  10. Disable subject areas that you don't want to expose in Oracle Analytics Server or that won't have a working connection.

    If connection information is missing, users see the message Fetch subject areas failed error when they view subject areas in Oracle Analytics Server.

  11. Use Consistency Check Manager to run a global consistency check.
  12. Save the changes to your semantic model file (RPD).