3 Upgrading Oracle Business Intelligence from 11g (Out-of-Place Migration)

Oracle has introduced many enhancements to existing features in the 12c release for Business Intelligence. Sometimes, these enhancements replace the existing functionality or reimplement it in a different way. Wherever possible, the existing 11g functionality and configuration is migrated to the corresponding 12c system. Although the appearance and behavior of the 12c system can be different, the end result is expected to be functionally equivalent. Review the flowchart and roadmap for an overview of the migration process for Oracle Business Intelligence from a 11g release.

An efficient migration strategy allows you to migrate your metadata and configuration from Oracle BI 11g to the 12c environment. The goal of this process is to not exactly replicate the appearance and behavior of the original 11g system in the 12c environment. Replicating the 11g appearance and behavior is time-consuming and sometimes difficult, if not impossible. For example, the dashboards and prompts are represented differently in 12c and would require significant manual intervention to recreate the 11g appearance. It also undermines the rationale behind moving on to Oracle BI 12c; namely, to take advantage of the enhancements that are introduced in 12c.

3.1 About the Oracle Business Intelligence Migration Process

During migration, you migrate your 11g metadata and configuration of the BI components that you have installed on your system. Migration is a two-step process. In the first step, you create an export bundle from a read-only 11g certified Release (11.1.1.7.0 or later) by using the BI Migration Tool (bi-migration-tool.jar). In the second step, you import the export bundle in to the 12c system by 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 as it is not a part of the 11g to 12c migration. If your users and groups are in an external LDAP, you must configure your Oracle BI 12c to point to the external LDAP. If your Oracle 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 you import 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 reenable them after the migration. Reenabling 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.

The following components are migrated:
  • Oracle BI Server: This includes the NQSConfig.INI and the opmn.xml files.

  • Oracle BI Presentation Services: This includes the instanceconfig.xml file.

  • Oracle BI Publisher: This includes the scanner.xml, xdo.cfg, xmlp-server-config.xml, datasources.xml, xdodelivery.cfg, cupsprinters.cfg files, the Map directory, and the Plugins directory.

The following metadata is migrated:

  • Content (WebCat), model (RPD), and the authorization policy securing it (Java AuthoriZatioN (JAZN).

The following OPMN properties contained in the opmn.xml file are not migrated to 12c during configuration migration:
  • obips
  • obiccs
  • obijh
  • obisch

However, the OBIS property is migrated.

Note:

The 11g system is left unchanged during and after the migration process is complete.

The following flowchart shows the flow of the migration process.

Figure 3-1 Migration Process Flowchart for Oracle Business Intelligence from 11g to 12c

Description of Figure 3-1 follows
Description of "Figure 3-1 Migration Process Flowchart for Oracle Business Intelligence from 11g to 12c"

Table 3-1 provides a high-level summary of the steps that you must perform to migrate from Oracle BI 11g to 12c.

Table 3-1 Tasks for Migrating Oracle Business Intelligence from 11g Release

Task Description

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating a non-SYSDBA user.

For a complete list of pre-upgrade tasks, see Pre-Upgrade Requirements.

Required

Review the prerequisites for 11g to 12c migration.

Make sure that you meet the necessary requirements before you migrate your metadata and configuration to 12c. Additionally, analyze and optimize your 11g system by removing redundant content and merging and consolidating similar content. For more information, see 11g to 12c Migration Prerequisites.

Required

Download and install the 12.2.1.4.0 Fusion Middleware Infrastructure and Oracle Business Intelligence distributions.

The Infrastructure distribution combines the WebLogic Server and the Java Required Files (JRF) that are required to set up the foundation to install other Fusion Middleware products.

As per the upgrade topology defined in this guide, you must install the Infrastructure in a new Oracle home.

The Oracle Business Intelligence distribution packs Oracle BI EE, Publisher, and Essbase.

You must install Oracle BI in the Oracle home that is created when you installed the 12.2.1.4.0 Infrastructure. To install the product distributions, follow the procedure that is described in Installing the Product Distributions.

Required

Create the required 12c schemas.

The schemas that you create will vary depending on your existing schema configuration.

To create schemas with the Repository Creation Utility (RCU), see Creating the Required 12c Schemas.

Required

Configure the 12c domain.

To configure the 12c domain with the Configuration Assistant, see Configuring Oracle BI Domain with the Configuration Assistant.

Required

Stop the servers and processes.

You must stop the 12c Oracle BI instance, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager before you start the migration. For the complete procedure, see Stopping Servers and Processes.

Required

Generate the BI Migration Tool (bi-migration-tool.jar) and copy it from the 12c Oracle home to the 11g system.

You must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh|cmd). For the complete procedure, see Generating the BI Migration Tool (bi-migration-tool.jar).

Required

Create an export bundle by using the BI Migration Tool on the 11g system.

The export bundle is a jar file and consists of the metadata information from the 11g Oracle home. To create the export bundle, see Creating the Export Bundle.

Required

Import the export bundle by using the BI Migration Script (migration-tool.sh|cmd).

You must import the export bundle by using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories. To import the bundle, see Importing with the BI Migration Script (migration-tool.sh|cmd).

Required

Start the servers and processes.

To start the 12c Oracle BI instance, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager, see Starting Servers and Processes.

Required

Verify the 12c deployment.

After you complete the migration procedure, run the Oracle BI Baseline Validation Tool to compare the 11g and 12c deployments. To verify whether the data from the 11g environment is correctly copied to the 12c environment, see Validating the Oracle BI Deployments.

Required

Complete the post-migration steps.

For Oracle BI EE post-migration steps, see Post-Migration Tasks for Oracle BI EE.

For Oracle BI Publisher post-migration steps, see Post-Migration Tasks for Oracle BI Publisher.

For Oracle Essbase post-migration steps, see Post-Migration Tasks for Essbase.

3.2 11g to 12c Migration 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 you proceed to the migration procedure:
  • 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. See Configuring Authentication Providers in Administering Security for Oracle WebLogic Server.

Make sure that you analyze and optimize the existing 11g system by removing redundant content and merging and consolidating similar content.

While analyzing the 11g system, note the following details:

  • Name and size of the repository
  • Name and size of the Oracle BI Presentation Catalog
  • Existing security model details
  • Data sources
  • Number of scheduled jobs
  • Any links to external systems

To optimize the existing 11g system, see:

3.2.1 Optimizing the 11g System

Migrating metadata and configuration from an existing Oracle BI 11g system requires time and resources. A poorly optimized 11g deployment can disrupt the migration process and can affect the performance of the 12c system. Oracle recommends that you analyze and optimize the existing 11g system by removing redundant content and merging and consolidating similar content.

To optimize the existing 11g system in readiness for migration:
  1. Run the Consistency Checker to check the validity of the 11g repository, and to identify and fix the syntax or semantic errors and warnings that can cause the queries to fail on the Oracle BI 12c Administration Tool. See Checking the Consistency of a Repository or a Business Model in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
  2. Disable the initialization blocks that are no longer being used.
  3. Identify and remove users and groups that are no longer required, and therefore do not need to be migrated.
  4. Identify and remove objects in the repository and the Oracle BI Presentation Catalog that are no longer required, and therefore do not need to be upgraded.
  5. If you have been using the Oracle BI Server usage tracking functionality, then review the usage tracking data to identify unused objects.
  6. If you have been using the Oracle BI Server summary advisor functionality, then review the summary advisor for aggregated data and aggregation script.

3.3 Installing the Product Distributions

Before you begin your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Business Intelligence 12c (12.2.1.4.0) distributions on the target system and install them by using Oracle Universal Installer.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.
To install the 12c (12.2.1.4.0) distributions:
  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    • Oracle Fusion Middleware Infrastructure (fmw_12.2.1.3.0_infrastructure_generic.jar)
    • Oracle Business Intelligence (UNIX: fmw_12.2.1.4.0_bi_platform_linux64.bin), (Windows: setup_fmw_12.2.1.4.0_bi_platform_win64.exe)
  3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.3.0_infrastructure_generic.jar

    • (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.3.0_infrastructure_generic.jar

  5. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select the following:
    • For Infrastructure, select Fusion Middleware Infrastructure.
    • For Oracle Business Intelligence, select BI Platform Distribution with Samples.
    Click Next.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  13. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
  14. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
    (UNIX) ./fmw_12.2.1.4.0_bi_platform_linux64.bin
    (Windows) setup_fmw_12.2.1.4.0_bi_platform_win64.exe

3.4 Creating the Required 12c Schemas

When upgrading from 11g, you must create the required 12c schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.

To create the required schemas:
  1. (Optional) If you are upgrading from 11g, and you wish to confirm the schemas which are present in your existing domain, then connect to the database as a user with DBA privileges, and run the following code from SQL*Plus:
    SET LINE 120
    COLUMN MRC_NAME FORMAT A14
    COLUMN COMP_ID FORMAT A20
    COLUMN VERSION FORMAT A12
    COLUMN STATUS FORMAT A9
    COLUMN UPGRADED FORMAT A8
    SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
    
  2. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.4.0), the certified JDK is 1.8.0_131 and later.
    Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
    • (UNIX) setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_131
    • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_131
    Add $JAVA_HOME/bin to $PATH.
  3. Go to the oracle_common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\bin
  4. Start the RCU:
    • (UNIX) ./rcu
    • (Windows) rcu.bat
  5. On the Welcome screen, click Next.
  6. On the Create Repository screen, select Create Repository and then select System Load and Product Load.
    If you do not have DBA privileges, select Prepare Scripts for System Load. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if the RCU were to execute the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can execute the script to complete the system load phase.

    Click Next.

  7. On the Database Connection Details screen, select the Database Type and enter the connection information for the database that hosts the 11g schemas. See the pertinent table below.

    Table 3-2 Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

    Option Description and Example
    Host Name

    Specify the name of the server where your database is running in the following format:

    examplehost.exampledomain.com

    For Oracle RAC databases, specify the VIP name or one of the node names in this field.

    Port

    Specify the port number for your database. The default port number for Oracle databases is 1521.

    Service Name

    Specify the service name for the database. Typically, the service name is the same as the global database name.

    For Oracle RAC databases, specify the service name of one of the nodes in this field. For example:

    examplehost.exampledomain.com

    Username Enter the user name for your database. The default user name is SYS.
    Password Enter the password for your database user.
    Role

    Select the database user's role from the drop-down list:

    Normal or SYSDBA

    Table 3-3 Connection Credentials for MySQL Databases

    Option Description and Example
    Host Name

    Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.

    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with administrator privileges.
    Password Enter the password for your database user.

    Table 3-4 Connection Credentials for Microsoft SQL Server Databases

    Option Description and Example
    Unicode Support

    Select Yes or No from the drop-down list.

    Server Name Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.

    MSSQL named instances: A named instance is identified by the network name of the computer and the instance name that you specify during installation. The client must specify both the server name and the instance name when connecting.

    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with administrator privileges.
    Password Enter the password for your database user.

    Table 3-5 Connection Credentials for IBM DB2 Databases

    Option Description and Example
    Server Name Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with DB Owner privileges. The default user name for IBM DB2 databases is db2admin.
    Password Enter the password for your database user.
    If the prerequisite check is successful, click OK to continue to the next screen. If the check fails, review the details you entered and try again.
  8. On the Select Components screen:
    1. Specify the custom prefix you want to use to identify the Oracle Fusion Middleware schemas.
      The custom prefix is used to logically group these schemas together for use in this domain. For the purposes of this guide, use the prefix FMW12213.
      Note the custom prefix that you have specified on this screen. You will need this later, during the domain creation process.
    2. Select AS Common Schemas and BIPLATFORM.
      When you select AS Common Schemas and BIPLATFORM, all of the schemas in this section are automatically selected. If the schemas in this section are not automatically selected, then select the required schemas.

      Common Infrastructure Services schema, also known as STB schema, is automatically created. You cannot select or deselect an STB schema. STB schema enables you to retrieve information from the RCU during domain configuration. For more information about the Service Table schema, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

      For more information about how to organize your schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.

  9. In the Checking Prerequisites dialog, verify that the prerequisites check is successful, then click OK.
  10. On the Schema Passwords screen, specify the passwords for your schema owners.
    Make a note of the passwords you enter on this screen as you will need this information while configuring your product installation.
  11. On the Map Tablespaces screen, configure the required tablespace mapping for the schemas you want to create.
    Click Next, then click OK in the confirmation dialog. When the progress dialog shows the tablespace creation is complete, click OK.
    You see the Encrypt Tablespace check box only if you have enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that the RCU creates.
  12. Verify the information on the Summary screen and click Create to begin schema creation.
    This screen contains information about the log files that were created from this RCU operation. Click on the name of a particular log file to view the contents of that file.
  13. Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation.

3.5 Configuring Oracle BI Domain with the Configuration Assistant

The Oracle BI 12c Configuration Assistant is a .sh (UNIX) or .cmd (Windows) file. Start the Configuration Assistant by starting the config executable from the bi/bin directory inside the Oracle home. Follow the procedure in this topic to complete the configuration step-by-step.

Note:

Oracle recommends that you use the Oracle BI 12c Configuration Assistant to configure your 12c system.
To configure the BI standard topology:

Note:

If you are extending the WebLogic domain with Oracle Business Intelligence by using the Configuration Assistant, make sure that the Administration Server for the domain is named AdminServer. Other names for the Administration Server are not supported.
  1. Change to the following directory:
    (UNIX) ORACLE_HOME/bi/bin
    (Windows) ORACLE_HOME\bi\bin
  2. Start the Configuration Assistant by entering the following command:
    (UNIX) ./config.sh
    (Windows) config.cmd
  3. Select the components to install and click Next.

    Note:

    To ensure that a consistent set of suites are deployed, the Configuration Assistant automatically adjusts your selection.
    • Essbase: Includes components such as Essbase Server, Cube Deployment Server, and Analytic Provider Services.
    • Business Intelligence Enterprise Edition: Includes components such as Presentation Services, Visual Analyzer, BI Composer, web services, proactive intelligence (Delivers and Actions), Web Services for SOA (WS4SOA), and Mobile Application Designer.
    • Business Intelligence Publisher: Includes Oracle BI Publisher.
  4. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.
    If any of the prerequisite checks fail, then a short error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or warning messages and continue with the installation, click Skip, although this approach is not recommended.

    Note:

    The configuration might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.
  5. On the Define New Domain screen, specify the following, and click Next:

    Table 3-6 Field-name descriptions for the Define New Domain screen

    Field Description
    Domains Directory Specify the path where you want to set up the domain directory.
    Domain Name Specify domain.
    Username Specify a username for the System Administrator.

    Note:

    This user is created in the embedded LDAP and is granted WebLogic Administrator permissions.
    Password Specify a password for the System Administrator.
    Confirm Password Confirm the password by reentering it.
  6. On the Database Schema screen, either create a new schema or use an existing schema by clicking the appropriate option.
    If you select to create a new schema, the Configuration Assistant creates a schema for you. Specify the following and click Next.

    Table 3-7 Field-name descriptions for the Database Schema screen

    Field Description
    Schema prefix Specify a unique schema prefix.
    Schema password Specify a password for your schema.
    Confirm password Confirm the password by reentering it.
    Database type Select the database that you are using from the list of values. Supported databases are:
    • Oracle Database

    • Microsoft SQL Server

    • IBM DB2

    Username Enter the privileged username to create the schema.
    Password Enter the password for the above username.
    Simple connect string The connect string that you specify varies depending on the type of database you are using.
    • (Oracle Database) host:port/service or host:port:SID or TNS connect string

    • (Microsoft SQL Server) //host:port;DatabaseName=dbname

    • (IBM DB2) //host:port;DatabaseName=dbname

    If you select to use an existing schema, you must create STB, BIPLATFORM, IAU, MDS, OPSS, and WLS schemas using the RCU. Specify the following and click Next.

    Note:

    If you are using Oracle Database version 12.2.0.1 or higher, you must create a pluggable database within a container database to create repository schemas. You cannot create schemas within a container database without using a pluggable database.
  7. On the Port Range screen, specify the port range and click Next.

    Note:

    The default, allocated port range is from 9500 to 9999, both inclusive. You can keep the default values or specify different values within this range.
  8. On the Initial Application screen, select one of the following options as per your requirement, and click Next:
  9. On the Summary screen, verify the values that you specified on each screen.
    Click Save to generate a response file used for silent installation (optional).
    Click Configure.
    The configuration process starts and the Configuration Progress screen is displayed.
  10. After the configuration concludes without any errors, click Next to go to the Configuration Complete screen.
  11. On the Configuration Complete screen, review the configuration summary.
    Click Save to save the information displayed on this screen in a file.
    Click Finish to close the Configuration Assistant.
    The BI Application opens in the browser. Use the login credentials that you specified while configuring to sign in to the BI application home.
You have configured the standard BI topology. The Configuration Assistant automatically starts the newly configured BI instance after successful completion. However, if you want to restart a domain that has been shut down manually, see Starting Servers and Processes.

3.6 Stopping Servers and Processes

Before you migrate your 11g metadata and configuration to 12c, stop the Oracle BI 12c instance, OBIS1, OBIPS1, Administration Servers, Managed Servers, and the Node Manager.

Note:

The procedure in this section describe how to stop servers and processes using the WLST command-line utility or a script. You can also use the Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager
To stop your Fusion Middleware environment:
  1. Change to the following directory:
    (UNIX) 12c_DOMAIN_HOME/bitools/bin
    (Windows) 12c_DOMAIN_HOME\bitools\bin
  2. To stop the Oracle BI instance and servers, enter the following command:
    (UNIX) stop.sh
    (Windows) stop.cmd

    Note:

    When prompted to enter the password, specify the Node Manager password that you entered while configuring the Oracle BI domain.

3.7 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. The BI Migration Script (migration-tool.sh|cmd) is available at the following location:
    (UNIX) 12c_DOMAIN_HOME/bitools/bin/
    (Windows) 12c_DOMAIN_HOME\bitools\bin\
  2. Run the following command to generate the BI Migration Tool:
    (UNIX) 12c_DOMAIN_HOME/bitools/bin/migration-tool.sh package bi-migration-tool.jar
    (Windows) 12c_DOMAIN_HOME\bitools\bin\migration-tool.cmd package bi-migration-tool.jar
    Where,

    Table 3-8 Command Description

    Option Description
    12c_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.

3.8 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:
    (UNIX) JDK_HOME/bin/java -jar bi-migration-tool.jar
    (Windows) 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 3-9 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:
    (UNIX) JDK_HOME/bin/java -jar bi-migration-tool.jar out ORACLE_HOME/Oracle_BI1 DOMAIN_HOME/tmp/migration-tool-test/test_export.jar
    (Windows) 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 3-10 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.

3.9 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 3-11 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:
    (UNIX) 12c_DOMAIN_HOME/bitools/bin/migration-tool.sh in config <export bundle> <service instance name>
    For example,
    12c_DOMAIN_HOME/bitools/bin/migration-tool.sh in config /tmp/migration-tool-test/test_export.jar ssi
    (Windows) 12c_DOMAIN_HOME\bitools\bin\migration-tool.cmd in config <export bundle> <service instance name>
    For example,
    12c_DOMAIN_HOME\bitools\bin\migration-tool.cmd in config /tmp/migration-tool-test/test_export.jar ssi
    Where,

    Table 3-12 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 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.

3.10 Starting Servers and Processes

After you migrate your 11g metadata and configuration to 12c, start the Oracle BI 12c instance, OBIS1, OBIPS1, Administration Servers, Managed Servers, and the Node Manager.

Note:

The procedure in this section describe how to start servers and processes using the WLST command-line utility or a script. You can also use the Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager
To start your Fusion Middleware environment:
  1. Change to the following directory:
    (UNIX) 12c_DOMAIN_HOME/bitools/bin
    (Windows) 12c_DOMAIN_HOME\bitools\bin
  2. To start the Oracle BI instance and servers, enter the following command:
    (UNIX) start.sh
    (Windows) start.cmd

    Note:

    When prompted to enter the password, specify the Node Manager password that you entered while configuring the Oracle BI domain.

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

You can download the Oracle BI Validation Tool from Oracle BI Baseline Validation Tool Downloads.

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