Migrating from Oracle BI 11g to 12c
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 process involves creating 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) and then importing it in to the 12c system.
This procedure is applicable only for Oracle BI EE and BI Publisher.
Oracle supports Essbase migration from Release 11.1.2.4 to Release 12.2.1. It is carried out using a separate command-line migration utility (EssbaseCagentToJagentMigrationUtility.sh|bat). To migrate Essbase data and metadata from 11.1.2.4 to 12.2.1, follow the procedure described in “Migrating Essbase 11.1.2.4 Data and Metadata to Essbase 12.2.1” in Oracle® Essbase Database Administrator's Guide 12.2.1.
This procedure is applicable only for Oracle BI EE and BI Publisher.
Oracle supports Essbase migration from Release 11.1.2.4 to Release 12.2.1. It is carried out using a separate command-line migration utility (EssbaseCagentToJagentMigrationUtility.sh|bat). To migrate Essbase data and metadata from 11.1.2.4 to 12.2.1, follow the procedure described in “Migrating Essbase 11.1.2.4 Data and Metadata to Essbase 12.2.1” in Oracle® Essbase Database Administrator's Guide 12.2.1.
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:- The WebLogic authentication configuration
- Mid-tier database content (such as BI Publisher schedules, the job history of agents, scorecard annotations, and usage tracking tables)
- Application-specific data such as TimesTen aggregates, the global cache, required database schemas, and Essbase applications, data, outlines, rules, and calculations
- Prerequisites
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 in order 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. - Creating the Export Bundle
The export bundle is a ".jar " file and consists of the metadata information from the 11g Oracle home. - 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
You must 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. - Next Step After Migration
To avoid authentication issues post migration, you must uncheck the Required for Authentication option in the DYNAMIC_OLAP_LOGIN initialization block. - 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 data from the 11g environment is correctly copied to the 12c environment.
