Clean Up and Reconfigure Your Semantic Model .rpd File

You must reconfigure data source connection information and clean up your semantic model .rpd file before you migrate content from Oracle BI Enterprise Edition to Oracle Analytics Cloud.

• Reconfigure connections to your data.
• Remove objects you no longer need or don't want to migrate to Oracle Analytics Cloud.
• Remove or disable objects that Oracle Analytics Cloud doesn’t support. If you have done so already, read Feature Availability and Comparison.
• Optimize query performance parameters for Oracle Analytics Cloud.

To edit the semantic model .rpd file:

1. Download the latest client tools for Oracle Analytics Cloud and the .rpd file from Oracle BI Enterprise Edition that you want to migrate.
   1. Download and install the latest client tools for Oracle Analytics Cloud from:

      http://www.oracle.com/technetwork/middleware/oac/downloads/oac-tools-4392272.html

      For instructions, see Download and Install Oracle Analytics Client Tools.

   2. Download the latest .rpd file from Oracle BI Enterprise Edition.
2. Use the latest Model Administration Tool to open the .rpd file you want to migrate.
3. Update database connection information.
   If you configured Data Gateway to enable access to your on-premise database or you moved your data to an Oracle Cloud 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 .rpd file connects to multiple databases, ensure that the settings for each connection pool are correct.
4. Delete unused database connections that you don't need anymore.
5. To optimize query performance, verify that the database parameters DEFAULT_BULK_FETCH_ROW_COUNT and MAX_BULK_FETCH_BUFFER_SIZE are set correctly for Oracle Analytics Cloud.
   1. In the Physical Layer pane, select the database connection you want to verify, and open the Feature pane.
   2. Verify the following parameters are above the minimum recommended values for Oracle Analytics Cloud to avoid latency issues.

      • DEFAULT_BULK_FETCH_ROW_COUNT: 1000 (minimum recommended value)

        If less than the minimum recommended value, increase to 1000. If set to a higher value, you can leave as-is.

      • MAX_BULK_FETCH_BUFFER_SIZE : 3276800 (minimum recommended value)

        If less than the minimum recommended value, increase to 3276800. If set to a higher value, you can leave as-is.

      
      Description of the illustration ceal_database_odw_settings.jpg
   3. Repeat these steps for each database in the physical layer.
6. 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.
   3. Remove any initialization blocks for authentication and authorization (set values for USER, ROLES or GROUP session variables).
7. Review any semantic model or session variables.
8. Disable subject areas that you don't want to expose in Oracle Analytics Cloud 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 Cloud.

9. Use Consistency Check Manager to run a global consistency check.
10. Save the changes to your .rpd file.
11. Make a note of the password that you set for the .rpd file.