Best Practices from Oracle Development's A‑Team

Completing the Migration from Business Intelligence Cloud Service to Oracle Analytics Cloud


This post is the second in a two-part series and details the tasks required to complete a migration from Business Intelligence Cloud Service (BICS) to Oracle Analytics Cloud (OAC) running on Oracle Cloud Infrastructure (OCI).

For details on preparing for the migration to OAC see Preparing to Migrate from Business Intelligence Cloud Service to Oracle Analytics Cloud.

This post uses the method of having Data Visualization project owners export and import their own projects. This may be the cleanest way to ensure that all the associated connections and data sets are properly migrated with the correct security settings.  An alternative method is to have an administrator attempt to change the security settings and possibly ownership of all DV objects prior to taking the snapshot and then attempt to change those settings back after the snapshot is migrated.


Published on November 28th, 2018.


Last Validated:    February 6th, 2019 with OAC 105.1.0-217 and BICS 18.1.5

Past Validations: November 9th, 2018 with OAC 18.3.3-69 and BICS 18.1.5


All migrations of Identity, Data Sources, APEX Applications, Network, and Compute have been performed.

The target OAC instance has been correctly sized and provisioned.


Importing Schema as a Service

Migrating the Snapshot

Migrating Non-Snapshot Objects


Administrators and users need the OAC URL.

Administrators need the BI Cloud Service Administrator role to upload and restore snapshots.

If importing the Schema Service Data, the Database Administrator role is required.

If using Remote Data Connector (RDC), the OAC Public Key is needed.

Users need the BI Dataload Author and the DV Content Author roles to import projects.

Importing Schema as a Service

If an RPD is used for the model, then the Schema Service is not used for reporting and this task can be skipped.

If the Schema Service contains business data that is used for reporting, then the data needs to be imported from a .dmp export file.

The overall documentation is at Data Pump Import. Refer to Copy Data from BICS Schema Service to BICS DBaaS or on On-Premise DB for an example.

If importing into ADW, this post provides a method: Importing into the Autonomous Data Warehouse using Oracle Data Pump

Migrating the Snapshot

The snapshot from BICS is uploaded and restored by an administrator. Users may then copy their private contents into their new private folder.

Uploading a Snapshot

Upload the BICS snapshot. Refer to Uploading Snapshots for the steps.

The snapshot contains:

Data Model

The data models created using the Thin Client Modeler (TCM)

-- or --

The RPD in use

Catalog Content

The Data Visualization (DV) projects and BI reports, dashboards, actions, action links, global variables, etc.

Not included are TCM Connections, Search Settings, and Deliveries

Application Roles

Default and custom application roles defined for your system.

Restoring a Snapshot

Refer to Restoring from a Snapshot for the steps. Restore all available objects.

 After the restore, some catalog objects need to be updated. Refer to Scan and Update Catalog Objects for the steps.

Restoring User Folders

When a user first connects to OAC, a private folder is created for them.

Users may optionally copy their objects from their private folder in the User Shared Folder to the new private folder. Below are the steps.

  1. 1. Open the Classic Home page (/analytics)
  2. 2. Click Catalog
  3. 3. Expand User Shared Folder
  4. 4. Expand the BICS private folder
  5. 5. Select all objects and click Copy








6. Select My Folders

7. Click Paste











Updating Data Model Connections

In this section, you finish configuring the TCM or the RPD.

Thin Client Models (Only if using TCM)

Create the Model Connections

Create all TCM connections as DV Console Connections with the details from the BICS service. Refer to Managing Database Connections for Data Models for the steps.

If the BICS connection named Default Connection is used, that connection is created using the new Schema name created in the DBCS for the BICS Schema Service data. DV Console Connections do not allow spaces in the name, so change the name appropriately.

Change any Models using the BICS default connection

Any models using the BICS Default Connection need to be changed to use the database connection created above. 

Modify/Validate/Publish the Models

For models whose database connection details changed from those in BICS, the model should be synchronized with the new connection. Refer to Refreshing and Synchronizing Source Objects and Data Model Objects for the steps.

Any modified models need to be published. Refer to Publishing Changes to Your Data Model for the steps.


If using an RPD, it needs to be upgraded to the latest version. If any of the data sources have changed, the relevant connection pools also need to be changed.

This step needs to be performed on a Windows Client.

Download the Administration Tool

Download and install the latest Administration Tool from OTN.

Open the RPD

Start the Administration tool.

If using RDC, load the java data sources before opening the RPD. Refer to Loading Java Data Sources for the steps.

Open the RPD.

Optionally Modify the Connection Pools

If any of the data sources have changed, update the appropriate connection pools. Refer to About Connection Pools for the steps.

Run the Consistency Check Manager

Run the Consistency Check Manager to detect any errors. Refer to Running the Consistency Check Manager for the steps.

Close and Upgrade the RPD

The RPD needs to be upgraded even if there were no changes. Close the RPD using File>Close.

Click Yes

Then close the Administration tool.







Update the RDC Public Key

If using RDC, obtain the public key from OAC and place it in the local RDC directory. Refer to Download and Deploy the Public Key for Your Cloud Service for the steps.

Configuring Custom Application Roles

If the RPD is using custom application roles for object or data level security, these need to be configured after a restore of the snapshot and before replacing the data model. Refer to Adding Your Own Application Roles for the steps.

Replace the Data Model

Upload and Replace the RPD using the DV Console. 

Migrating Non-Snapshot Objects

Some objects do not come over in a snapshot or are not available to an administrator after the migration. This section covers the remaining steps.

Importing DV Projects

In order for DV connections and data sets to be updated properly, project owners import their own projects. If a project owner is not available, the administrator may import projects. Refer to Import an Application or Project for the steps.

Configuring Custom Application Roles

If you are using custom roles in a RPD, this step is part of the RPD steps above.

The custom application roles need to be configured after a restore of the snapshot. Refer to Adding Your Own Application Roles for the steps.

Configuring the Search Settings

If BICS is using Search Indexing then OAC needs to be configured. Refer to Configuring Search Indexing for the steps.

Update the user for the Data Model searches. For the Catalog, update the indexing options to match the settings in BICS.

Creating Deliveries

If BICS is using Deliveries then OAC needs to be configured.

Setting up an Email Server

Refer to Setting Up an Email Server to Deliver Reports for the steps.

Emailing Reports

Refer to Emailing Reports for the steps.


This post detailed the steps required to complete a migration from Business Intelligence Cloud Service to Oracle Analytics Cloud. 

For more OAC, BICS and BI best practices, tips, tricks, and guidance that the A-Team members gain from real-world experiences working with customers and partners, visit http://www.ateam-oracle.com/dayne-carley


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha