This chapter describes how to upgrade an existing Oracle BI Publisher 10g Release 3 (10.1.3.4 or later) environment to Oracle BI Publisher 11g.
This chapter contains the following sections:
Task 1: Understand the Starting Points for BI Publisher Upgrade
Task 2: Decide Upon an Oracle Business Intelligence Topology
Task 3: Run RCU to Create the Destination BIPLATFORM Schemas
Task 7: Perform Any Required Post-Upgrade Configuration Tasks
For information about starting points for a BI Publisher upgrade, see Chapter 3, "Supported Starting Points for Oracle Business Intelligence Upgrade." If you are running a version of BI Publisher older than the 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, see Oracle Fusion Middleware Patching Guide, which provides information about applying the latest Oracle Fusion Middleware patches.
This guide provides instructions for upgrading from BI Publisher 10g to the latest BI Publisher 11g.
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 BI Publisher 11g integration with Oracle WebLogic Server and Oracle Fusion Middleware applications.
For more information, see "Understanding Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.
The Repository Creation Utility (RCU) is a graphical tool for creating and managing Oracle Fusion Middleware database schemas in the database. To create the BI Publisher 11g destination schema, see "Create Database Schema Using the Repository Creation Utility" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
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 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 is displayed 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.
Note:
If you have already run RCU to create the destination BIPLATFORM schema for Oracle BI EE, then you are not required to perform Task 3. Oracle BI EE and BI Publisher share the BIPLATFORM schema.Use the Oracle Business Intelligence 11g installer to install BI Publisher 11g on a separate host computer. Do not install Oracle Business Intelligence 11g on a computer that is running Oracle Business Intelligence 10g, because this installation scenario is not supported.
See the following topics for more information:
When you install BI Publisher 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:
The BI Publisher Repository 10g directory
The E-Business Data Template 10g directory
If the 10g installation directories are 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 6-1 for information about specifying the source details for these components on the Specify Source Details screen of Upgrade Assistant.
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.
Note:
If you have already installed Oracle BI EE and selected the option to install BI Publisher, then you are not required to perform Task 4.Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the BI Publisher Repository.
Note:
You can upgrade the BI Publisher Repository and Scheduler schema in any order.Before you start Upgrade Assistant, follow these steps:
Back up the 10g and 11g repositories.
Choose the upgraded BI Publisher 11g repository path. This can be the same as the installed 11g repository path, for example, \user_projects\domains\bifoundation_domain\config\bipublisher\repository. It can also be a new path on the server, for example, D:\MyUpgradedBIPRepository\repository. If you choose a new path for the upgraded repository, then copy the content of 11g repository to this new path.
Stop the Managed Server on which BI Publisher is running if the environment is using the BI Publisher catalog (file-based). If you choose a new path for the upgraded repository, then the Upgrade Assistant utility will simply upgrade all your 10g catalog contents to this location. Any seeded 11g content (such as the Sample Files) will not be included.
The Administration Server should remain running.
For information on what is upgraded by Upgrade Assistant, see Section 1.4, "Understanding BI Publisher Upgrade."
For a descriptions of the security model upgrade path, see Section 1.4.1.2, "Security Model Changes."
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.For more information, see "Using the Upgrade Assistant Command-Line Interface" in Oracle Fusion Middleware Upgrade Planning Guide.
Table 6-1 Running Upgrade Assistant to Upgrade the BI Publisher Repository
| Step | Screen | Description and Action Required |
|---|---|---|
|
1 |
None. |
To start Upgrade Assistant using the graphical user interface: Change directory to the For UNIX: ./ua On a Windows operating system: ua.bat |
|
2 |
Click Next to continue. |
|
|
3 |
Select Upgrade Oracle BI Publisher Repository. Click Next to continue. |
|
|
4 |
Select Upgrade 10g BI Publisher Repository Directory or Upgrade E-Business Suite Data Template Directory. For Upgrade 10g BI Publisher Repository Directory, enter, or browse to the Repository Directory. For Upgrade E-Business Suite Data Template Directory, enter, or browse to the Data Template Directory. Note: Upgrade Assistant does not support reading the data definition from the E-Business Suite environment. Store the data template XML files in a file system and run Upgrade Assistant to create an equivalent data model definition in the BI Publisher Enterprise Server. Click Next to continue. |
|
|
5 |
In the Repository Directory field, enter the destination 11g BI Publisher Repository directory if you selected the 10g BI Publisher Repository Directory as the source directory. The default location of the destination repository is MWHOME\user_projects\domains\bifoundation_domain\config\bipublisher\repository. However, this destination repository path can be any path on the server. Enter the 11g data model directory if you selected the E-Business Suite Data Template Directory as the source. Click Next to continue. |
|
|
6 |
Enter the following:
Click Next to continue. |
|
|
7 |
During the examination process, Upgrade Assistant checks for the following:
Under the Status column, the word succeeded should appear. If instead, the word failed appears, inspect the log file for details. Click Upgrade. |
|
|
8 |
Click Upgrade to continue. |
|
|
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. |
||
|
9 |
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.Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the BI Publisher Scheduler schema.
Upgrade Assistant is installed automatically into the bin directory of the Oracle Fusion Middleware Oracle home.
Note:
You can upgrade the BI Publisher Repository or Scheduler schema in any order.Upgrade Assistant performs the schema upgrade by upgrading source BI Publisher Scheduler schema content into the destination BI Publisher Scheduler schema content.
Table 6-2 Running Upgrade Assistant to Upgrade the BI Publisher Scheduler Schema
| Step | Screen | Description and Action Required |
|---|---|---|
|
1 |
None. |
To start Upgrade Assistant using the graphical user interface: Change directory to the For UNIX: ./ua On a Windows operating system: ua.bat |
|
2 |
Click Next to continue. |
|
|
3 |
Select Upgrade Oracle BI Publisher Scheduler Schema. Click Next to continue. |
|
|
4 |
Enter the details for the database that hosts the BI Publisher 10g Scheduler: 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 |
Enter the details for the database that hosts the Oracle Fusion Middleware 11g BI Publisher 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 connection string. 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 |
Enter the 11g BI Publisher schema name from the drop-down list. 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 |
Upgrade Assistant examines the following:
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 |
Click Upgrade. |
|
|
9 |
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 |
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.See Section 8.2, "Post-Upgrade Tasks and Considerations for BI Publisher" for a description of the post-upgrade tasks that you might need to perform for each of the BI Publisher components.
To verify that the BI Publisher upgrade was successful, see Section 5.8, "Task 8: Verify the Oracle BI EE Upgrade."