The migration process migrates your 11g metadata and configuration for the BI components that you have installed on your system. Migration is a two-step process. The first step in the process is to create an export bundle from a read-only 11g certified Release (11.1.1.7 or later) using the BI Migration Tool (bi-migration-tool.jar). The second step is to import the export bundle in to the 12c system using the BI Migration Script (migration-tool.sh).
Note:
The export process is read-only. Data, configuration, or existing binaries are not modified or deleted on the source system. During export, the metadata and configuration (specifically the data model and connection pools), the catalog content, and the security store authorization policy are retained. You must reconfigure the following:WebLogic does not support migration from 11g to 12c. Therefore, you must reconfigure the security realm in 12c and is not a part of the 11g to 12c migration. If your users and groups are in an external LDAP, you must configure your BI 12c to point to the external LDAP. If your BI 11g users were hosted in the WebLogic LDAP, you can use the WebLogic Server to export users from 11g in to 12c WebLogic LDAP. However, 12c does not support a BI System User. Therefore, you must delete the BI System User after importing it in to the 12c system.
The Agents are migrated from 11g to 12c in a disabled state. You must re-enable them after the migration. Re-enabling the agents recreates the entries in the scheduler database. However, the Agent history is not migrated from 11g to 12c. You must also reconfigure Usage Tracking.
The import process is offline. During import, metadata content is deployed to customize the specified service instance and it overwrites the existing configuration settings.
Ensure that you configure the environment as per Oracle recommendations in readiness for the migration.
For a procedure to start and stop Administration server and Managed servers, see Starting and Stopping Administration and Managed Servers and Node Manager and for a procedure to start and stop the BI instance, see Starting and Stopping Components in Oracle Fusion Middleware Administering Oracle Fusion Middleware.
You have the JDK version 1.8.0_101 installed on your system.
You have stopped OBIS1 and OBIPS1.
The BI Migration Tool (bi-migration-tool.jar) is self-executing and self-contained. You must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script is made available after you configure the 12c domain. This step packages the components of the BI Migration Tool into a single, self-executing jar file, so that it can be easily transported on to an 11g system. To do this, you must have access to a 12c system with a configured domain. You must set up the 12c domain to provide sufficient infrastructure to run the BI Migration Tool and allow it to repackage itself. The 12c domain can be empty at this stage.
The export bundle is a ".jar " file and consists of the metadata information from the 11g Oracle home.
You must import the export bundle using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories.
Table 2-4 Parameter Description: Importing the export bundle
Parameter | Description |
---|---|
in | Indicates the BI Migration Script to import the bundle. |
config | Indicates the BI Migration Script to overwrite the configuration files during the import process. This allows you to also migrate the configuration along with the data. |
<export bundle> | The path where the export bundle is located. |
<service instance name> | Specifies the name of the service instance, which is ssi. |
Note:
The default service instance name is "ssi". However, if you install Oracle BI in a silent mode using a response file, you can specify a service instance name during the product installation. In that case, you must specify the service instance name you have specified in the response file.Note:
It takes about 10 more minutes for the Application roles and policies to migrate after the migration process is complete.After completing the import process, you must start OBIS1 and OBIPS1 which you stopped before beginning the migration process.
The Oracle BI Baseline Validation Tool enables you to identify differences during life cycle operations, such as migrating from the Oracle BI 11g release to the 12c release. After you complete the migration procedure, you can use this tool to compare the two deployments and verify whether the data from the 11g environment is correctly copied to the 12c environment.
For more information about using the Oracle BI Validation Tool, see Comparing Oracle Business Intelligence Deployments Using the Oracle Business Intelligence Baseline Validation Tool.
Note:
You can download the Oracle BI Validation Tool along with the other Oracle Business Intelligence download on the Oracle Technology Network. See the Readme document that is included in the Oracle BI Validation Tool download for more information. For specific information on the distributions you want to download for each product, see Oracle Fusion Middleware Download, Installation, and Configuration Readme Files page.