5 Upgrading Oracle Business Intelligence Enterprise Edition

This chapter describes how to upgrade an existing Oracle Business Intelligence Enterprise Edition (Oracle BI EE) 10g Release 3 (10.1.3.2 or later) environment to Oracle Business Intelligence 11g.

This chapter contains the following sections:

Task 1: Understand the Starting Points for Oracle BI EE Upgrade
Task 2: Decide Upon an Oracle Business Intelligence Topology
Task 3: Run RCU to Create the Destination BIPLATFORM Schemas
Task 4: Install and Configure Oracle BI EE 11g
Task 5: Upgrade the Oracle BI Repository and Catalog
Task 6: Upgrade the Oracle BI EE Scheduler Schema
Task 7: Perform Any Required Post-Upgrade Configuration Tasks
Task 8: Verify the Oracle BI EE Upgrade

5.1 Task 1: Understand the Starting Points for Oracle BI EE Upgrade

For information about starting points for an Oracle Business Intelligence upgrade, see Chapter 3, "Supported Starting Points for Oracle Business Intelligence Upgrade." If you are running a version of Oracle Business Intelligence older than version specified in Chapter 3, then you must upgrade to the supported starting point version before attempting to upgrade to 11g.

If you are already running Oracle Fusion Middleware 11g, then see Oracle Fusion Middleware Patching Guide, which provides information about applying the latest Oracle Fusion Middleware patches.

This guide provides instructions for upgrading from Oracle Business Intelligence 10g to the latest Oracle Business Intelligence 11g.

5.2 Task 2: Decide Upon an Oracle Business Intelligence Topology

To help you decide on a target topology for the Oracle Business Intelligence 11g deployment, see Chapter 4, "Oracle Business Intelligence for 10g Users," which compares 10g and 11g features, directory structures, and architecture. It also describes Oracle Business Intelligence 11g integration with Oracle WebLogic Server and Oracle Fusion Middleware applications.

5.3 Task 3: Run RCU to Create the Destination BIPLATFORM Schemas

The Repository Creation Utility (RCU) is a graphical tool for creating and managing Oracle Fusion Middleware database schemas.

Important screens when running RCU:

Database Connection Details screen — Select the type of database on the system. This is the database in which you create the Oracle Business Intelligence schemas. Provide the necessary credentials for RCU to be able to connect to the database.
Select Components screen — Near the top of the screen, select Create a New Prefix. The default prefix is DEV. You can provide another prefix, if preferred.

Expand the Business Intelligence component group by clicking the plus sign (+) next to it. Then, click Business Intelligence Platform so that a check appears next to it. This action automatically selects the Metadata Services (MDS) schema (under the AS Common Schemas group), which is also required by Oracle Business Intelligence.

To create the Oracle BI EE 11g destination schema, see "Create Database Schemas Using the Repository Creation Utility" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

5.4 Task 4: Install and Configure Oracle BI EE 11g

Use the Oracle Business Intelligence 11g installer to install Oracle Business Intelligence 11g on a separate host computer. Do not install Oracle Business Intelligence 11g on a computer that is running Oracle Business Intelligence 10g, as this installation scenario is not supported.

For more information, see the following topics:

Section 5.4.1, "Availability of the 10g Oracle BI Repository and Catalog Files"
Section 5.4.2, "Important Notes When Installing Oracle Business Intelligence 11g in Preparation for Upgrade"

5.4.1 Availability of the 10g Oracle BI Repository and Catalog Files

When you install Oracle Business Intelligence 11g, ensure that the following 10g source directories are accessible to the Oracle Business Intelligence 11g Upgrade Assistant, which you run from the Business Intelligence 11g Oracle home. Upgrade Assistant must be able to browse to and access these directories:

Directories that contain the 10g Oracle BI repository files
The 10g Catalog and Catalog Deliveries directories

If the 10g installation is not available to Upgrade Assistant, then you can make them available in other ways. For example, you can copy them to a shared network disk or to a USB drive.

For more information, see Table 5-1 for information about specifying the source details for these components on the Specify Source Details screen of Upgrade Assistant.

5.4.2 Important Notes When Installing Oracle Business Intelligence 11g in Preparation for Upgrade

Important screens when running the Oracle Business Intelligence Installer:

Select Installation Type screen — Select Enterprise install for new installations. This option Installs a new Oracle Business Intelligence system for a hosted deployment on one or more computers.
Create or Scale Out BI System screen — Click Create New BI System.
Specify Installation Location screen — Specify the Oracle Middleware home location.
Database Details screen — Specify the database type, the database connection string, and the user name and password for the Business Intelligence Platform schema.

For installation and configuration instructions for Oracle BI EE, see "Enterprise Install for New Installations" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

5.5 Task 5: Upgrade the Oracle BI Repository and Catalog

Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the Oracle BI repository and Catalog.

5.5.1 Before Running Upgrade Assistant

Before running Upgrade Assistant configure TNSNAMES.ora in the 11g system so that it connects to any databases that are used by the Oracle BI repository.

In addition, any custom changes to the Oracle BI EE 10g configuration files, for example, instanceconfig.xml, are not upgraded by Upgrade Assistant. You must manually edit the 11g configuration files to re-apply the customizations.

The following configuration changes might be necessary before running Upgrade Assistant:

Confirm that any data sources that are used by the Oracle BI repository are configured in the 11g system.
If you configured the nqsconfig.ini file in the 10g system for database authentication, then you must copy over the same configurations to the 11g version of the files.

For example, to add the following parameter in the nqsconfig.ini file for this type of authentication:
```
SECURITY
AUTHENTICATION_TYPE = DATABASE;
DATABASE
DATABASE = "mydb";
```
For more information about using the nqsconfig.ini file in Oracle Business Intelligence 11g, see "NQSConfig.INI File Configuration Settings" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

5.5.2 Administration Server and Managed Servers

The Administration Server and the Managed Server must remain running during the upgrade process.

5.5.3 Running Upgrade Assistant

Upgrade Assistant is installed automatically into the bin directory of the Oracle Fusion Middleware Oracle home. For information on the Oracle home, see Section 4.1, "Oracle Business Intelligence 11g and Oracle WebLogic Server."

Note:

The following sections describe how to use the Upgrade Assistant in graphical user interface mode. You can also use the Upgrade Assistant command line to perform these tasks.

For more information, see "Using the Upgrade Assistant Command-Line Interface" in Oracle Fusion Middleware Upgrade Planning Guide.

Table 5-1 Running Upgrade Assistant to Upgrade the Oracle BI Repository and Catalog

Step	Screen	Description and Action Required
1	None.	To start Upgrade Assistant using the graphical user interface, change the directory to the `ORACLE_HOME/bin` directory of the Oracle Fusion Middleware installation: Note: If you have multiple Oracle BI repositories, you must run Upgrade Assistant once for each Oracle BI repository. For UNIX: ./ua On a Windows operating system: ua.bat
2	Welcome Screen	Click Next to continue.
3	Specify Operation	Select Upgrade Oracle BI RPD and Catalog. Click Next to continue.
4	Specify Source Details	Enter the details for the source 10g Oracle BI repository and Catalog. This could be in the existing 10g installation, or a copy made to a shared network location or USB drive: Upgrade Repository (RPD) RPD File: Enter the name of the Oracle BI repository file. Administrator User Name: Enter the 10g Administrator User Name. Typically the name is `Administrator`. Administrator Password: Enter the 10g Administrator Password Enter the password which will be used to secure the upgraded 11g RPD: The repository password does not have to match the Administrator or any other password. Upgrade Catalog Catalog Directory: Enter the name, or browse to the Catalog Directory. Catalog Deliveries Directory: In 10g, the `deliveries` directory is a special directory used for data such as Dashboard snapshots used by Briefing Books. The directory is called `deliveries` by default and is located in the OracleBIData/web/catalog directory. In many cases, the 10g directory is empty. If the 10g `deliveries` directory is not available, any empty directory named `deliveries`, can be given for upgrade. If Upgrade Assistant finds a directory called `deliveries` in the same folder as the catalog, it is selected by default. Click Next to continue.
5	Specify WebLogic Server	Enter the following: In the Host field is always `localhost` for this type of upgrade. In the Port field, enter the server's port number, for example, 7001. In the Username field, enter the administrator user name, for example, weblogic. In the Password field, enter the password associated with the specified administrator user. Click Next to continue.
6	Examining Components	During the examination process, Upgrade Assistant checks for the following: The source directory exists. The source directory is readable and contains a file for upgrade. Under the Status column, the word succeeded should appear. If instead, the word failed appears, inspect the log file for details. Click Next to continue.
7	Upgrade Summary	Click Upgrade.
8	Upgrading Components	The upgrade process begins, and is completed when the status bar reaches 100 percent. If there are errors during the upgrade, inspect the log file for details. The log files are located in the following directory: BI_ORACLE_HOME/upgrade/logs/ua<timestamp>.log For Windows Operating Systems: BI_ORACLE_HOME\upgrade\logs\ua<timestamp>.log Where <timestamp> is the current date and time. You can also check the component log files, in directories organized by component under ORACLE_INSTANCE\diagnostics\logs Click Next to continue.
9	Upgrade Complete	Click Close.

Note:

Review the log for any errors or warnings. Resolve any errors or warnings in 10g files and resolve them manually in the upgraded 11g repositories and catalogs.

5.6 Task 6: Upgrade the Oracle BI EE Scheduler Schema

The 10g iBots (called agents in 11g) are stored entirely in the Oracle BI Presentation Catalog. If you upgrade the catalog, then you have all the agents, but they will not run automatically. (The scheduler schema holds the list of jobs that the scheduler runs, including agents).

You could choose to re-enable the agents in the catalog instead of upgrading the scheduler schema. This is a valid use case as you might want to enable a subset of agents for test purposes after upgrading.

Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the Oracle BI EE Scheduler schema to the new BIPLATFORM schema.

Upgrade Assistant is installed automatically into the bin directory of the Oracle Fusion Middleware Oracle home.

Note:

The following sections describe how to use the Upgrade Assistant in graphical user interface mode. You can also use the Upgrade Assistant command line to perform these tasks.

To see an online description of the Upgrade Assistant command line options type the following command:

ua -help

For more information, see "Using the Upgrade Assistant Command-Line Interface" in Oracle Fusion Middleware Upgrade Planning Guide.

Upgrade Assistant performs the Scheduler schema upgrade by upgrading source schema content into the destination Oracle Business Intelligence Scheduler schema content.

Table 5-2 Running Upgrade Assistant to Upgrade the Oracle BI EE Scheduler Schema

Step	Screen	Description and Action Required
1	None.	To start Upgrade Assistant using the graphical user interface: Change the directory to the `ORACLE_HOME/bin` directory of the Oracle Fusion Middleware installation: For UNIX: ./ua On a Windows operating system: ua.bat
2	Welcome	Click Next to continue.
3	Specify Operation	Select Upgrade Oracle BI Scheduler Schema. Click Next to continue.
4	Specify Source Database	Enter the details for the database that hosts the Oracle BI EE 10g Scheduler schema: Database Types: Select the database type from the drop-down list. Connect String: Enter the second portion of the connection string. Examples of the appropriate syntax for this field appear immediately below the field. Source Schema: Enter the name of the existing 10g schema/database/user. Password: Enter the password associated with the specified source schema. DBA Username: To log in as the Oracle SYS database account specify SYS AS SYSDBA in this field. DBA Password: Enter the password associated with the specified DBA Username. Click Next to continue.
5	Specify Target Database	Enter the details for the database that hosts the Oracle BI EE 11g BI Scheduler target database: Target Database Types: The target database type is based on the source database type. Connect String: Enter the second portion of the JdbcConnectionString. Examples of the appropriate syntax for this field appear immediately below the field. Password: Enter the password associated with the specified source schema. DBA Username: To log in as the Oracle SYS database account specify SYS AS SYSDBA in this field. DBA Password: Enter the password associated with the specified DBA Username. Click Next to continue.
6	Specify Schema Name	Enter the 11g BI schema name for the target database. Schema Name: Select BIPLATFORM schema from the drop-down list, which has a prefix that is defined when you create the schema with RCU. Password: Enter the password associated with the specified schema. Click Next to continue.
7	Examining Components	Upgrade Assistant examines the components and checks that the source and target schemas contain the expected columns. Under the Status column, the word succeeded should appear. If instead, the word failed appears, inspect the log file for details. Click Next to continue.
8	Upgrade Summary	Click Upgrade.
9	Upgrading Components	The upgrade process begins, and is completed when the status bar reaches 100 percent. If there are errors during the upgrade, inspect the log file for details. The log files are located in the following directory: BI_ORACLE_HOME/upgrade/logs/ua<timestamp>.log For Windows Operating Systems: BI_ORACLE_HOME\upgrade\logs\ua<timestamp>.log Where <timestamp> is the current date and time. Click Next to continue.
10	Upgrade Complete	Click Close.

Note:

Review the log file for any errors or warnings. Resolve any errors or warnings found in the 10g files manually in the upgraded 11g repositories and catalogs.

5.7 Task 7: Perform Any Required Post-Upgrade Configuration Tasks

See Section 8.1, "Post-Upgrade Tasks and Considerations for Oracle Business Intelligence Enterprise Edition" for a description of the post-upgrade tasks you might need to perform for Oracle BI EE components.

Note:

Check the final Upgrade Assistant screen for suggested manual upgrade steps.

5.8 Task 8: Verify the Oracle BI EE Upgrade

You can verify that Oracle BI EE has been upgraded successfully by logging into the 11g system to confirm that the Oracle BI EE components are up and running.

You can also verify the upgrade using either of the following methods:

Run the Upgrade Assistant again and select Verify Instance on the Specify Operation page.

Follow the instructions on the screen for information on how to verify that specific Oracle Fusion Middleware components are up and running.
Use the Fusion Middleware Control to verify that the Oracle Business Intelligence components are up and running.

For more information, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in Oracle Fusion Middleware Administrator's Guide.