| Oracle® Business Intelligence Applications Fusion Edition Upgrade Guide Version 7.9.5 Part Number E12084-01 |
|
|
View PDF |
| Oracle® Business Intelligence Applications Fusion Edition Upgrade Guide Version 7.9.5 Part Number E12084-01 |
|
|
View PDF |
This section contains instructions for upgrading Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3, and 7.9.4 when you are running Siebel CRM Applications as your source system.
This section includes the following topics:
Section 5.3, "Upgrading to Informatica PowerCenter Release 8.1.1, SP4"
Section 5.4, "Configuring Informatica PowerCenter Release 8.1.1, SP4 to Work with the DAC"
Section 5.7, "Upgrading the Data Warehouse Schema and Migrating Data"
Upgrade the Oracle BI Infrastructure to the version that is supported for this release of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications Fusion Edition for the current version that is supported. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Business Intelligence Infrastructure Upgrade Guide.
Run the Oracle BI Applications installer to upgrade your Oracle BI Applications environment to the current version. For instructions on running the installer, see the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide.
Note:
Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.Note:
If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for Oracle BI Applications release 7.9.5. If you do not uninstall the old release, some release 7.9.5 folders will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release.)The current release of Oracle BI Applications supports Informatica PowerCenter 8.1.1, Service Pack 4 (SP4). You must install both Informatica PowerCenter 8.1.1 and SP4 to run the current release of Oracle BI Applications.
The components and architecture for Informatica PowerCenter 8.1.1 differ significantly from Informatica PowerCenter 7.x. Oracle recommends that you carefully review the Informatica documentation. The Informatica PowerCenter 8.1.1 SP4 documentation is included in the Informatica PowerCenter DVD provided with Oracle BI Applications.
For a summary of installation instructions for installing Informatica PowerCenter 8.1.1 and SP4 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide. For instructions on configuring Informatica PowerCenter components for use with Oracle BI Applications, see the section in the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide that covers configuring Informatica PowerCenter components.
For detailed information about deploying Informatica 8.1.1, refer to the Informatica PowerCenter Installation and Configuration Guide, and related documentation.
To upgrade to Informatica PowerCenter Release 8.1.1, SP4
Perform the pre-upgrade steps documented in the Informatica PowerCenter Installation and Configuration Guide.
Install Informatica PowerCenter Release 8.1.1 and SP4, following the instructions in the Informatica PowerCenter Installation and Configuration Guide.
Perform the post-upgrade steps documented in the Informatica PowerCenter Installation and Configuration Guide.
Note:
The Informatica PowerCenter 8.1.1 installation process includes upgrading your current Informatica repository to the release 8.1.1 format. This process is necessary so that you will be able to access your current repository using release 8.1.1 client tools so that you can perform the procedure Section 5.5, "Upgrading the Informatica Repository."In Section 5.5, "Upgrading the Informatica Repository" you back up and rename your current repository and then restore the Informatica repository (Oracle_BI_DW_Base.rep) that is installed during the Oracle BI Applications installation. You then copy your custom folder from the backed up repository into the newly restored Oracle_BI_DW_Base repository.
Informatica PowerCenter Version 8.1.1, SP4 requires additional configuration steps in order to work with the DAC. For instructions on performing these steps, see the following sections in the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide.
Enabling DAC client communication with Informatica PowerCenter
Enabling DAC server communication with Informatica PowerCenter
Registering Informatica Services in the DAC
Follow this procedure to upgrade the Informatica repository.
To upgrade the Informatica repository
Make sure you have backed up and renamed your current Informatica repository.
For instructions, see the Informatica documentation, which is included in the Informatica PowerCenter DVD provided with Oracle BI Applications.
Note:
This repository must be upgraded during the procedure in Section 5.3, "Upgrading to Informatica PowerCenter Release 8.1.1, SP4." You must upgrade this repository to the release 8.1.1 format in order to move your custom folder from this repository into the new Oracle_ BI_DW_Base repository that you restore in the steps below.Copy the Oracle_BI_DW_Base.rep file from the folder OracleBI\dwrep\Informatica\Repository into the folder \Informatica\PowerCenter8.1.1\server\infa_shared\Backup.
Note:
The Oracel_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 5.2, "Upgrading Oracle BI Applications."Restore the Oracle_BI_DW_Base.rep repository.
For instructions, see the Informatica PowerCenter Installation and Configuration Guide, which is included in the Informatica PowerCenter DVD provided with Oracle BI Applications.
Copy the custom folder from your previous Informatica repository to the newly created Informatica repository:
Launch the Informatica PowerCenter Repository Manager, and connect to both your previous and newly created Informatica repositories.
Copy the Custom folder in your previous repository into the newly created Informatica repository.
Make sure there is an individual workflow for each of the mappings in the Custom folder.
Before you begin this procedure, do the following:
Determine what customizations were made to your existing DAC repository.
Make sure you have renamed and backed up your existing DAC repository into a different database. When you backup the DAC repository, you export the DAC metadata, in XML format (using the DAC's Export tool), into a folder other than the standard DAC export folder where backups are stored (DAC\export). For instructions on exporting DAC metadata, see the Oracle Business Intelligence Data Warehouse Administration Console Guide.
To upgrade the DAC metadata repository
Upgrade your current DAC repository tables to be compatible with the new DAC repository release.
Configure the new DAC client version to read the DAC metadata from your existing DAC repository.
Log in to the DAC and select Yes if prompted to upgrade the repository tables.
Export all the applications from your custom repository (including the custom applications) to a folder other than the standard DAC export folder (DAC\export) or the folder into which you backed up metadata in the previous format.
Import the new DAC metadata for your application from the standard DAC export folder (DAC\export). Select the Truncate Repository Tables check box.
For instructions on importing DAC metadata, see the Oracle Business Intelligence Data Warehouse Administration Console Guide.
Refresh the source system container to locate any missing objects in your customized application.
In the DAC menu bar, select File, then select Refresh Source System Containers.
A list of available source system containers appears in the container list to the right of the View buttons.
Select the appropriate source system container from the list, and click OK.
Confirm that you want to refresh the source system container.
Rebuild all the subject areas and execution plans in your customized application to include any new changes in the object dependency. For information about building subject areas and execution plans, see the Oracle Business Intelligence Data Warehouse Administration Console Guide.
This section contains the following topics:
Section 5.7.1, "Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data"
Section 5.7.2, "Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data"
If you are currently running Oracle BI Applications release 7.9.0, 7.9.1, 7.9.2, or 7.9.3, you need to perform the procedures in Section 5.7.1 and Section 5.7.2.
If you are currently running Oracle BI Applications release 7.9.4, you only need to perform the procedure in Section 5.7.2.
These procedures add new tables, columns, and indexes to the existing data warehouse schema. They also modify the existing data warehouse schema objects.
You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, or 7.9.3.
To upgrade the data warehouse schema and migrate data into the upgraded data warehouse
Run the 792_UPGRADE_PRE_CTL_SCRIPT.sql script.
Open the SQL client for your database type, for example, SQLPLUS for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 792_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
Use the DDLimp utility to run the ddl_794.ctl script, which is located in the OracleBI\dwrep\Upgrade\CTLFiles folder. Use the following command:
..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string> /G SSE_ROLE /I N /R Y /F <..\OracleBI\dwrep\ddl_794.ctl> /L <..\oracleBI\dwrep\ddl_794.log>
For example:
DDLIMP /U SADMIN /P SADMIN /C OBIA /G SSE_ROLE /I N /R Y /F C:\OracleBI\dwrep\ddl_794.ctl /L C:\OracleBI\dwrep\ddl_794.log
Run the 792_UPGRADE_PRE_DIMENSION_SCRIPT.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 792_UPGRADE_PRE_DIMENSION_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
If you upgraded your transactional database to Siebel Applications 8.0 or 8.1, run the workflows to migrate your data into the upgraded data warehouse.
In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.
Run the following workflows in the order indicated:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
Verify the data migrated successfully by checking whether any of the Informatica mapping log files stored in the \Informatica PowerCenter 8.1.1\server\infa_shared\SessLogs directory indicate errors or failures.
If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the main Informatica repository (Oracle_BI_DW_Base.rep).
Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the reset_infa_seq_gen.bat file.
The file opens a command prompt, which will prompt you for the parameters listed below.
Enter the appropriate parameter values to reflect your environment (the parameters are database specific).
For Oracle databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the data warehouse database user ID |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main InformaticaRepository database |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the main Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
For Microsoft SQL Server databases:
| Parameter | Setting |
|---|---|
OLAP_SERVER |
Enter the name of the SQL Server for the OLAP database |
OLAP DATABASE |
Enter the name of the database on which OLAP data is available |
OLAP USERNAME |
Enter the user ID of the data warehouse database |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA SERVER ADDRESS |
Enter the name of the SQL Server for the Informatica Repository database. |
INFORMATICA DATABASE |
Enter the name of the database on which the Informatica Repository metadata is available |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main Informatica Repository database |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password of the main Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
For IBM DB2 databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the user ID of the data warehouse database |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password @connection string of the main Informatica Repository database |
INFA DATABASE ALIAS |
Enter the name of the database in which Informatica Repository metadata is available |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3, or 7.9.4.
To upgrade the data warehouse schema and migrate data into the upgraded data warehouse
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the reset_infa_seq_gen.bat file.
The file opens a command prompt, which will prompt you for the parameters listed below.
Enter the appropriate parameter values to reflect your environment (the parameters are database specific).
For Oracle databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the data warehouse database user ID. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the Upgrade InformaticaRepository database. |
INFORMATICA REPOSITORY |
Enter the name of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value UPGRADE. |
For Microsoft SQL Server databases:
| Parameter | Setting |
|---|---|
OLAP_SERVER |
Enter the name of the SQL Server for the OLAP database. |
OLAP DATABASE |
Enter the name of the database on which OLAP data is available. |
OLAP USERNAME |
Enter the user ID of the data warehouse database. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA SERVER ADDRESS |
Enter the name of the SQL Server for the Informatica Repository database. |
INFORMATICA DATABASE |
Enter the name of the database in which the Informatica Repository metadata is available. |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password @connection string of the Upgrade Informatica Repository database. |
INFORMATICA REPOSITORY |
Enter the name of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value UPGRADE. |
For IBM DB2 databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the user ID of the data warehouse database. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password @connection string of the Upgrade Informatica Repository database. |
INFA DATABASE ALIAS |
Enter the name of the database in which Informatica Repository metadata is available. |
INFORMATICA REPOSITORY |
Enter the name of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the Upgrade Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value UPGRADE. |
Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql script.
Open the SQL client for your database type, for example, SQLPLUS for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 795_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
Run the UPGRADE_795.ctl script.
This script adds temp tables for the upgrade process.
Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
Use the DDLimp utility to run the UPGRADE_795.ctl script. Use the following command:
..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string> /G SSE_ROLE /I N /R Y /F <..\OracleBI\dwrep\UPGRADE_795.CTL> /L <..\oracleBI\dwrep\UPGRADE.log>
For example:
DDLIMP /U SADMIN /P SADMIN /C OBIA /G SSE_ROLE /I N /R Y /F C:\OracleBI\dwrep\UPGRADE_795.CTL /L C:\OracleBI\dwrep\UPGRADE.log
Notes:
/P <PASSWORD> - The password for the data warehouse.
/C <ODBC connect string> - The name of the ODBC connect string.
/I N - Tells DDLimp to ignore the indexes DDL defined in the CTL file if any exist. It does not change existing indexes. (The default is /I Y, which tells DDLimp to create and merge indexes from the CTL file with the indexes in the database.For Oracle databases, use the Data Direct drivers.
In addition, you can use the following commands:
/W Y - If the OLAP database is Oracle and Unicode.
/Z Y - If the OLAP database is DB2 or SQL Server and Unicode.
/B <TABLE_SPACE_NAME> - If you want to create these tables in a separate table space. For DB2, This must be specified as 32K tablespace.
/X <INDEX_TABLE_SPACE_NAME> - If you want to create the indexes in a separate tablespace. For DB2, This must be specified as 32K tablespace.
/Y - Storage File for DB2/390.
/R - Regrant tables.
Use the DDLimp utility to run the ddl_795.ctl script, which is located in the OracleBI\dwrep\Upgrade\CTLFiles folder. Use the following command:
..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string> /G SSE_ROLE /I N /R Y /F <..\OracleBI\dwrep\ddl_795.ctl> /L <..\oracleBI\dwrep\ddl_795.log>
For example:
DDLIMP /U SADMIN /P SADMIN /C OBIA /G SSE_ROLE /I N /R Y /F C:\OracleBI\dwrep\ddl_795.ctl /L C:\OracleBI\dwrep\ddl_795.log
Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder \Informatica PowerCenter 8.1.1\server\infa_shared\LkpFiles.
Migrate data into the upgraded data warehouse.
Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 8.1.1\server\infa_shared\Backup.
Launch the Informatica PowerCenter Administration Console and restore Upgrade.rep (located in Informatica PowerCenter 8.1.1\server\infa_shared\Backup).
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 795_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 8.1.1\server\infa_shared\SrcFiles.
Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.
Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the adapter setup.
In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and create one relational connection based on the appropriate database platform for your OLTP database. Create the connection with the name PARAM_OLTP.
Note:
If you are connected to an Oracle database, use the Oracle Native driver instead of ODBC.If you are connected to a SQL Server database, use the ODBC driver rather than the native SQL Server driver.
In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and create one relational connection based on the appropriate database platform for your OLAP database. Create the connection with the name PARAM_OLAP.
Note:
If you are connected to an Oracle database, use the Oracle Native driver instead of ODBC.If you are connected to a SQL Server database, use the ODBC driver rather than the native SQL Server driver.
In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.
Verify the data migrated successfully.
Check whether any of the Informatica mapping log files stored in the \Informatica PowerCenter 8.1.1\serva\infa_shared\Sesslogs directory indicates errors or failures.
Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.
Check the log file for the script Upgrade_795.ctl that you ran using the DDLimp command to determine whether any of the runs failed.
If you did not detect any errors or failures in the steps above, then the data migration was successful.
Note:
Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tablesIf the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.
Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.
In the Informatica PowerCenter Administration Console, select the Upgrade repository service.
In the General Properties area of the Properties tab, click Edit .
Make sure the operating mode of the repository service is set to Exclusive.
Click OK.
Choose Actions, and then click Delete Contents.
In the Delete contents for <repository name> dialog, enter the repository username and password (for example, Administrator/Administrator), then click OK.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the main Informatica repository (Oracle_BI_DW_Base.rep).
Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the reset_infa_seq_gen.bat file.
The file opens a command prompt, which will prompt you for the parameters listed below.
Enter the appropriate parameter values to reflect your environment (the parameters are database specific).
For Oracle databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the data warehouse database user ID. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main InformaticaRepository database. |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the main Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR. |
For Microsoft SQL Server databases:
| Parameter | Setting |
|---|---|
OLAP_SERVER |
Enter the name of the SQL Server for the OLAP database. |
OLAP DATABASE |
Enter the name of the database on which OLAP data is available. |
OLAP USERNAME |
Enter the user ID of the data warehouse database. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA SERVER ADDRESS |
Enter the name of the SQL Server for the Informatica Repository database. |
INFORMATICA DATABASE |
Enter the name of the database on which the Informatica Repository metadata is available. |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main Informatica Repository database. |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password of the main Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR. |
For IBM DB2 databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the user ID of the data warehouse database. |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database. |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database. |
INFORMATICA DB PASSWORD |
Enter the password @connection string of the main Informatica Repository database. |
INFA DATABASE ALIAS |
Enter the name of the database in which Informatica Repository metadata is available. |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository. |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository. |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the Informatica Repository. |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the name of the machine that runs the Repository Service for the Upgrade Repository. |
INFA_PORT |
Enter the port number for the Repository Service. The default is 6001. |
INFA_FOLDER |
Enter the value HOR. |
This process merges your customizations of a prior release of the Oracle BI repository with the new version of the Oracle BI repository. Before you begin this process, make sure you have backed up and renamed your existing repository.
To upgrade the repository, perform the following tasks:
Section 5.8.1, "Preparing for the Oracle BI Repository Upgrade"
Section 5.8.5, "Regression Testing the Oracle BI Repository Merge"
The tasks in this section refer to multiple versions of the Oracle BI repository. Table 5-1 provides the names and descriptions of the repositories used in the examples in this section.
Table 5-1 Names of Analytics Repositories used in Examples
| Name of Repository | Description |
|---|---|
|
OracleBIAnalyticsApps_79x.rpd |
The standard Oracle BI repository for the version you are upgrading from. Note: Standard repositories from previous releases are available in the folder \OracleBI\Upgrade. |
|
OracleBIAnalyticsApps.rpd |
The standard Oracle BI repository for the version you are upgrading to. |
|
Customer_OracleBIAnalyticsApps.rpd |
The Oracle BI repository that contains your customizations for the version you are upgrading from. |
|
Merged_Repository_OracleBI.rpd |
The Oracle BI repository that contains your customizations for the version you are upgrading to. |
Follow this procedure to prepare for the repository upgrade.
To prepare for the Analytics repository upgrade
Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:
Original
AfterEqualize
AfterMerge
AfterManualWork
AfterRegressions
Copy the original repository (for example, OracleBIAnalyticsApps_79x.rpd), the production repository (for example, Customer_OracleBIAnalyticsApps.rpd, and the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) into the folder \OracleBIUpgrade\Original.
If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.rpd file and use this as your original repository. (If you have the original repository that you extracted during the last upgrade, you can use it as the original repository file.) This will prevent you from losing any new metadata you would like to add in this upgrade.
Also, if you customized the Oracle BI repository by trimming a large number of objects and you would like to get those objects back during the current upgrade, you need to trim the OracleBIAnalyticsApps_79x.rpd file in the same way and use the modified version as the original repository file. This will prevent you from losing any new metadata you would like to add in this upgrade.
The Merge feature in the Administration Tool relies on a change detection algorithm to determine the changes that need to be made to upgrade repositories correctly. For the algorithm to work correctly, it has to determine which objects in the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.
The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.rpd.
Equivalence between objects is established using the Administration Tool's Equalize feature. The file that you specify in the Output option (-O) is the only file that is modified during the equalization process.
The Equalize feature has several mechanisms for determining whether an object in two different repositories is semantically the same:
Fully Qualified Name. If an object in one repository has the same fully qualified name as another object of the same class in another repository, then the two objects are declared equal.
Simple String Substitution. Equivalence can be declared between two objects of the same class in two repositories whose only difference is that some key characters in their names differ. The equalizerpds executable file ignores those characters while checking fully qualified names. For example, "Core"."W_DAY_D" might be considered equivalent to "Core"."W DAY D" if the characters "_" and " " have been declared as equivalent.
Rename File. When none of the preceding rules are applicable, equivalence can be manually declared using a script as input to the equalizerpds executable file. Oracle ships the rename files (MAP) for the major releases. The files are located in the OracleBI\Upgrade folder. You can also create your own rename files for customizations not covered in the files that Oracle ships. You can open and edit the rename files in Microsoft Excel.
The syntax of the equalizerpds command is as follows:
equalizerpds.exe -A userid1 [-B [password1]] -C base_repository_name -D userid2 [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-X] [-Y equalStringSet] -X Treat 'Factxxxx' as 'Fact' in Business Model. -Y Treat the characters as equals. /? Display this usage information and exit.
To equalize a repository
Copy the appropriate MAP file from the OracleBI\Upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.
Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_79x.rpd). An example of the equalizerpds command is as follows:
equalizerpds -A Administrator -B SADMIN -C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd -D Administrator -E SADMIN -F \\OracleBIUpgrade\Original\OracleBIAnalyticsApps.rpd -O \\OracleBIAnalyticsUpgrade\AfterEqualize\OracleBIAnalyticsApps.rpd -X -J rename7x-79.map
The MAP files are located in the \OracleBI\Upgrade folder.
If the equalizerpds.exe executable file runs correctly, no errors are returned.
Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:
equalizerpds -A Administrator -B SADMIN -C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd -D Administrator -E SADMIN -F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.rpd -O \\OracleBIUpgrade\AfterEqualize\Customer_OracleBIAnalyticsApps.rpd
The execution of equalizerpds that equalizes the customer repository with the original repository does not use the rename file.
Make sure that the original repository is copied unchanged into its new location so that after running the script, all three repositories are contained within the \OracleBIUpgrade\AfterEqualize directory.
To verify the process completed successfully, compare the size of the repositories. The output repository (-O) should be close to the same size as the repository you equalized (-F).
Follow this procedure to compare your existing repository with the new version to which you are upgrading.
To compare the Analytics repositories
Use the Administration Tool's Compare Repositories feature to analyze the differences between your existing repository and the new version of the repository to which you are upgrading. Note where elements have been created, removed, or changed in the new version. Consider whether you can use the new metadata and retire customizations you made in the existing repository.
For instructions on how to use the Administration Tool's Compare Repositories feature, see Oracle Business Intelligence Server Administration Guide.
In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Business Intelligence Server Administration Guide.
To merge versions of the Oracle BI repositories
Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.
Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.
Save the repository with a new name, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
This new repository will contain the final results of the upgrade.
From the Administration Tool menu bar, select File, then select Merge.
In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).
Enter the password, and click OK.
Click Select for the Modified Repository field.
In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.
Click Open, type the password, and then click OK.
In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.
To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Merge button is enabled.
Click Merge.
This process can take up to 40 minutes, depending on the size of the repositories you are working with. A message will alert you when the merge is complete.
Click Yes when asked if you want to run a consistency check.
The number of errors returned by the consistency check is an indication of how successful the merge process was. If you receive many errors, for example, over 300, you should analyze the reason for the errors. If the merge process failed to recognize that two objects are the same, you may need to edit the rename file if the object is in the Current repository, or add your own rename file if you have renamed many of the objects and the upgrade engine failed to relate them to the original objects.
You also may need to change the actions you selected in the Decision drop-down list before rerunning the merge. This could save you time by reducing the number of errors that you will need to fix manually.
Once you are satisfied with the results of the merge, you should fix the remaining errors manually. It is important that you fix all errors before moving on to the next step. This repository serves as the input for the next stage.
You should also check that all of your customized objects are present and that no duplicate physical tables were introduced. To check for duplicate tables, search for physical tables using a query such as:
where name like '*#1'
Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.
In performing a regression test for the repository merge, the objective is to collect a set of logical SQL statements that are used for reports and to verify that they continue to work with the new metadata. For this purpose, it is recommended that you perform the following procedure.
To perform regression testing
Run the reports that are necessary to include in the regression suite. These reports might be a subset of the reports in the Presentation Catalog.
Collect the logical SQL generated in the previous step. You can do this using Usage Tracking or by parsing the query log file.
For information about Usage Tracking, see Oracle Business Intelligence Server Administration Guide.
Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in \OracleBI\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Business Intelligence Server Administration Guide.
Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.
Execute the edited logical SQL against the merged repository, and save the results.
Compare the results from the steps above and try to explain the differences. If it is determined that these differences are due to the upgrade process, then you have to correct them manually.
This repository now contains the merged content from the new OracleBIAnalyticsApps.rpd and the production repository.
You will need to upgrade your current Oracle BI Presentation Catalog if your organization:
Has prebuilt applications already installed, and
Has customized the current Oracle BI Presentation Catalog
If you made no changes to the previous Presentation Catalog distributed with previous versions of prebuilt applications, you do not need to upgrade the catalog. You can begin using the newer version of the catalog.
This process includes the following tasks:
Section 5.9.2, "Upgrading the Oracle BI Presentation Catalog to a Newer Version"
Section 5.9.3, "Testing the Results of the Presentation Catalog Upgrade"
Caution:
In releases of Oracle BI Applications previous to 7.9, the Presentation Catalog (formerly known as the Siebel Analytics Web Catalog) was stored in a single file rather than in a directory structure of individual files. If you have a previous version of the Presentation Catalog, you will need to convert it to the new format. For more information about how to convert the Presentation Catalog to the new format, see the Oracle Business Intelligence Infrastructure Upgrade GuideBefore you upgrade and merge your current Presentation Catalog with the new Presentation Catalog, determine which of the existing content you want to keep and which new content you want to incorporate. Review your existing Presentation Catalog and determine the usage patterns of reports and dashboards. Note that some of the preconfigured content in the existing catalog may appear in the new version in a redesigned format. In addition, the new version includes completely new content. After you have decided the content that is to make up your enterprise Presentation Catalog, trim the input catalogs using the Catalog Manager. For information on trimming catalogs, see Oracle Business Intelligence Presentation Services Administration Guide.
The Presentation Catalog upgrade process makes use of three catalogs:
The original Presentation Catalog. This is the unmodified Presentation Catalog that you received with the Oracle BI Applications release that you are upgrading from.
The new Presentation Catalog. This is the Presentation Catalog that is installed in the OracleBIData\web\catalog folder with the installation of Oracle BI Applications.
The current Presentation Catalog. This is the Presentation Catalog currently in use at your organization.
You use Catalog Manager for this upgrade process. Catalog Manager compares the content in both the Current Presentation Catalog and the Modified Presentation Catalog with the content in the Original Presentation Catalog, merges any changes into the Current Presentation Catalog, and produces a list of upgrade differences, which you must resolve by indicating how you want the differences handled. If the catalogs have conflicting content, you can choose which catalog the content should be taken from. The end result is a merged Presentation Catalog that contains the site-specific changes, as well as new metadata.
To upgrade your Presentation Catalog to a newer version
Make a backup copy of the current Presentation Catalog, rename the folder <catalogname>_old, and move it to a temporary location.
Copy the original Presentation Catalog into the folder that holds your current Presentation Catalog and rename it <catalogname>_Original.
Start Catalog Manager and open the new Presentation Catalog in offline mode.
Select Tools, then select Upgrade Catalog.
In the original Presentation Catalog field, browse to locate the original Presentation Catalog.
In the Current Presentation Catalog field, browse to locate your current Web Catalog, <catalogname>_old.
Click OK.
Resolve any upgrade differences as follows:
Review each unresolved difference in the Unresolved differences list.
For each unresolved difference, select the version that you want to keep.
Click OK.
The log file SiebelAnalyticsMigrationLog.txt holds information about the merge process. This log file is written to \OracleBI\web\catalogmanager. If you get an error logged in the file, this means that the path in question had a problem that did not allow the merge mechanism to resolve the merge. No action was taken. To merge that particular item, go into your original Presentation Catalog and merge it manually.
Review the upgraded Presentation Catalog, and, if necessary, set permissions for objects.
Save the new Presentation Catalog.
Note:
Before you perform this step, you must first migrate the data into the upgraded data warehouse.The Presentation Catalog upgrade functionality does not automatically carry over object permissions; therefore, you should review the Presentation Catalog object permissions before you perform this step.
This step ensures that the upgraded reports and the new preconfigured reports are functional and render correct results within the new, merged Presentation Catalog. This step is typically performed by visually inspecting the final results of the complete end-to-end upgrade process.
For upgraded reports, the preferred approach for comparison purposes is to have side-by-side environments, and have users review specific dashboard content between the two environments. Examine not only the look and feel of the application but also the data contained in the reports to make sure the content remains the same. It is recommended that you request users to use various elements of the user interface to validate results, such as global prompts, column selectors, report filters, drills, and navigations, as they normally do on a day-to-day basis.
Also review the overall visibility and administrative settings in the new Presentation Catalog to ensure they are correct. Pay careful attention to the visibility rules that are established for any content that was migrated during the upgrade. You might have to manually adjust these settings.
