2 Migrating from Oracle BI 11g to 12c

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:
  • 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.

2.1 Prerequisites

Ensure that you configure the environment as per Oracle recommendations in readiness for the migration.

Make sure that you have met the following requirements before proceeding to the migration procedure:
  • You have an 11g certified release (11.1.1.7, 11.1.1.8, and 11.1.1.9) installed.
  • You have installed and configured the 12c software as per the instructions in Oracle Fusion Middleware Installing and Configuring Oracle Business Intelligence Installation Guide.
  • You have file system permission on both the 11g and 12c systems.
  • You have configured the WebLogic authentication chain to enable the 11g users to sign in to the 12c domain. For more information, see Configuring Authentication Providers in Oracle Fusion Middleware Administering Security for Oracle WebLogic Server.
  • You have stopped the 12c BI instance, in case it is running. The BI instance should not be running before migrating content into the new 12c instance.

    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.

2.2 Generating the BI Migration Tool (bi-migration-tool.jar)

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.

To generate the BI Migration Tool jar:
  1. Locate the BI Migration Script available at the following location:
    On UNIX operating system:
    DOMAIN_HOME/bitools/bin/migration-tool.sh
    On Windows operating system:
    DOMAIN_HOME\bitools\bin\migration-tool.cmd
    Replace the DOMAIN_HOME with the actual path to the 12c Domain home you created when you configured the 12c BI instance.
  2. Run the following command to generate the BI Migration Tool:
    On UNIX operating system:
    DOMAIN_HOME/bitools/bin/migration-tool.sh package bi-migration-tool.jar
    On Windows operating system:
    DOMAIN_HOME\bitools\bin\migration-tool.cmd package bi-migration-tool.jar
    Where,

    Table 2-1 Command Description

    Option Description
    DOMAIN_HOME/bitools/bin Specifies the location of the BI Migration Script.
    package Specifies the BI Migration Script to perform the packaging operation.
    bi-migration-tool.jar Specifies the file name of the migration tool jar file where the output is written. In this documentation, the bi-migration-tool.jar file is referred as the "BI Migration Tool" and the migration-tool.sh script is referred as the "BI Migration Script".
  3. Copy the BI Migration Tool to the host system from where you want to export data.

2.3 Creating the Export Bundle

The export bundle is a ".jar " file and consists of the metadata information from the 11g Oracle home.

To create an export bundle:
  1. Change to the directory where you created the bi-migration-tool.jar file.
  2. Run the BI Migration Tool without passing parameters. Enter the following command:
    On UNIX operating system:
    JDK_HOME/bin/java -jar bi-migration-tool.jar
    On Windows operating system:
    JDK_HOME\bin\java -jar bi-migration-tool.jar
    This command displays the list of parameters that you can include for the BI Migration Tool to locate various parts of the 11g system.
  3. Run the BI Migration Tool with the following parameters this time to create an export bundle.

    Table 2-2 Parameter Description: Creating Export Bundle

    Parameter Description
    out Indicates the BI Migration Tool to run in Export mode.
    <oracle 11g home> Specifies the Oracle home directory. This is typically the directory Oracle_BI inside Middleware home.
    DOMAIN_HOME Specify the Domain home directory. This is typically the directory user_projects/domains/bi/ inside the Middleware home.
    <output export bundle path> Specifies the file name of the export bundle where the output is written. The output is not a BAR file. The file name of the export bundle must include the "jar" extension.
    Following is a sample command for creating an export bundle:
    On UNIX operating system:
    JDK_HOME/bin/java -jar bi-migration-tool.jar out ORACLE_HOME/Oracle_BI1 DOMAIN_HOME/tmp/migration-tool-test/test_export.jar
    On Windows operating system:
    JDK_HOME\bin\java -jar bi-migration-tool.jar out ORACLE_HOME/Oracle_BI1 DOMAIN_HOME\tmp\migration-tool-test\test_export.jar
    Where,

    Table 2-3 Parameter Values: Creating Export Bundle

    Parameter Description
    ORACLE_HOME/Oracle_BI1 The path where the Oracle home directory is located.
    DOMAIN_HOME The path where the Domain home directory is located.
    /tmp/migration-tool-test/test_export.jar The location where the export bundle is created.

    Note:

    Make sure to replace these file paths with the respective paths on your system.
    The following message indicates a successful export:

    Export succeeded

Copy the export bundle in to the 12c system.

2.4 Importing with the BI Migration Script (migration-tool.sh|cmd)

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.

You can include the following parameters while running the BI Migration Script to import the export bundle in to the 12c system:

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.
To import the metadata and configuration in to the 12c system:
  1. Run the BI Migration Script with the following parameters:
    On UNIX operating system:
    DOMAIN_HOME/bitools/bin/migration-tool.sh in config <export bundle> <service instance name>
    For example,
    DOMAIN_HOME/bitools/bin/migration-tool.sh in config /tmp/migration-tool-test/test_export.jar ssi
    On Windows operating system:
    DOMAIN_HOME\bitools\bin\migration-tool.cmd in config <export bundle> <service instance name>
    For example,
    DOMAIN_HOME\bitools\bin\migration-tool.cmd in config /tmp/migration-tool-test/test_export.jar ssi
    Where,

    Table 2-5 Parameter Values: 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.
    /tmp/migration-tool-test/test_export.jar The path where the export bundle is located.
    ssi Specifies the name of the service instance.
  2. If the migration is successful, you see the output such as the following:
    Import succeeded
    About to close down logging to: DOMAIN_HOME/bilogs/migration/migration-2016-05-05-06-13-05.log
    This is so that the log file can be archived into the diagnostics zip
    Any remaining log entries will go to '/tmp/migration.log', and will not appear in the diagnostics zip
    Migration action succeeded
    
You can now start the 12c system. For more information about starting the 12c system, see About Managing Oracle Business Intelligence Processes in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

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.

2.5 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.

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.