Migrating the metadata from Oracle BI 11g to 12c is a two-step process, and is carried out by using the BI Migration Script (migration-tool.sh). The first step in the process is to create an export bundle from a read-only 11g certified Release (220.127.116.11 or later) using the BI Migration Tool (bi-migration-tool.jar). The second step is to import the previously-generated export bundle in to the 12c system. The BI Migration Script is used to generate the BI Migration Tool jar file.
This procedure is applicable only for Oracle BI EE and BI Publisher.
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:
The WebLogic authentication configuration
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.
Mid-tier database content (such as BI Publisher schedules, the job history of agents, scorecard annotations, and usage tracking tables)
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.
Application-specific data such as TimesTen aggregates, the global cache, required database schemas, and Essbase applications, data, outlines, rules, and calculations
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.
Generating the BI Migration Tool jar File
The BI Migration Tool is self-executing and self-contained. You must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh). The BI Migration Script is made available after you install the 12c software. 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.
Importing the Export Bundle Using the BI 12c Configuration Assistant
You can use the Oracle BI 12c Configuration Assistant to reference the export bundle while configuring the 12c system if you have installed but have not configured the 12c system. Follow the procedure in this topic only if you are configuring the 12c system for the first time. However, if you have already configured the 12c system, you have the BI domain and BI Service instance created. Perform the procedure to import the export bundle using the BI Migration Script.
Performing an Import Using the BI Migration Script
Use the BI Migration Script (migration-tool.sh) to import the 11g data in to the 12c system, if you have already configured the 12c system. The BI Migration Script automatically determines the Oracle home and the Domain home directories.
Validating the Oracle BI Deployments
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 results from the 11g environment are the same as the results from the 12c environment.