Skip Headers
Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users
Release 7.9.6.3
Part Number E19040-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

8 Upgrading Oracle BI Applications for JD Edwards Source Systems

Note:

Some of the information about database platforms and source systems might not apply to this version of Oracle Business Intelligence Applications. For up-to-date information about supported databases and source systems in this version of Oracle Business Intelligence Applications, make sure you read System Requirements and Supported Platforms for Oracle Business Intelligence Applications. Make sure that you also read the Oracle Business Intelligence Applications Release Notes. The most up-to-date versions of these documents are located on the Oracle Technology Network at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/index.html. To register for a free account on the Oracle Technology Network, go to http://www.oracle.com/technetwork/index.html.

This section contains instructions for upgrading Oracle BI Applications when you are running JD Edwards Enterprise Applications as your source system

This section contains the following topics:

8.1 Upgrading Oracle BI Infrastructure

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 for the current version that is supported. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

8.2 Upgrading Oracle BI Applications

Run the Oracle BI Applications installer to upgrade your Oracle BI Applications environment to the current version. For instructions on running the installer, see Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

Note the following points:

8.3 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

The components and architecture for Informatica PowerCenter 9.0.1 differ significantly from previous versions. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation, which is included on the Informatica DVD provided with Oracle BI Applications.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica PowerCenter Administrator Guide, and related documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2

Note the following points:

8.4 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide, which is included on the Informatica DVD provided with Oracle BI Applications.

To upgrade the Informatica Repository

  1. Make sure you have backed up and renamed your current Informatica Repository.

    Note:

    This repository must be upgraded to the version 9.0.1 format during the procedure in Section 8.3, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2." You must upgrade this repository to the version 9.0.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.

  2. Copy the Oracle_BI_DW_Base.rep file from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

    Note:

    The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 8.2, "Upgrading Oracle BI Applications."

  3. Restore the Oracle_BI_DW_Base.rep repository into an empty schema.

  4. Copy the custom folder from your previous Informatica Repository to the newly created Informatica Repository:

    1. Launch the Informatica PowerCenter Repository Manager, and connect to both your previous and newly created Informatica repositories.

    2. Copy the Custom folder in your previous repository into the newly created Informatica Repository.

    3. Make sure there is an individual workflow for each of the mappings in the Custom folder.

8.5 Configuring Informatica PowerCenter Version 9.0.1 to Work with Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 requires additional configuration steps to work with Oracle BI Applications and DAC. For instructions on performing these steps, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

8.6 Upgrading and Configuring DAC

This section includes information you must follow to upgrade and configure DAC. It includes the following topics:

8.6.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current version of DAC is installed by its own installer and not the Oracle BI Applications installer. For information about the version of the DAC platform supported with the current release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metadata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

  • Installing and Setting Up the DAC Platform

    Note:

    You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

  • Installing DAC Metadata Files

  • Logging into DAC for the First Time and Importing Metadata into the DAC Repository

    After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications version 7.9.6.3.

8.6.2 Configuring the DAC Client and Server to Work with Oracle BI Applications and Informatica

You need to perform certain configuration tasks to enable the DAC Client and Server to work with Oracle BI Applications and Informatica PowerCenter. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

  • Configuring the DAC Server

  • Configuring DAC Integration Settings

  • Configuring the SiebelUnicodeDB Custom Property

    Note:

    This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

  • Setting Up DAC to Receive Email Notification

  • Additional Configuration Tasks

    In this section, perform only the tasks that apply to your environment.

8.6.3 Upgrading the DAC Repository

You will use the Refresh Base option of the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option of the Upgrade/Merge Wizard, see the topic titled, "About the Refresh Base Option," in "Chapter 10: Upgrading, Comparing and Merging DAC Repositories," in the Oracle Business Intelligence Data Warehouse Administration Console User's Guide.

The Oracle Business Intelligence Data Warehouse Administration Console User's Guide is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

Before you upgrade the DAC Repository, do the following:

  • Make a copy of your default source system container. (You cannot change the metadata in the preconfigured container. You must make a copy of it in order to be able to modify the objects it contains.) For instructions, see the Oracle Business Intelligence Data Warehouse Administration Console User's Guide.

8.7 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

Perform the procedures in this section if you are upgrading from Oracle BI Applications release 7.9.6, 7.9.6.1, or 7.9.6.2 to release 7.9.6.3.

This section includes the following procedures:

If you are currently running Oracle BI Applications release 7.9.6, you need to perform the procedures in Section 8.7.1, Section 8.7.2, and Section 8.7.3.

If you are currently running Oracle BI Applications release 7.9.6.1, you need to perform the procedures in Section 8.7.2 and Section 8.7.3.

If you are currently running Oracle BI Applications release 7.9.6.2, you need to perform the procedures in Section 8.7.3.

8.7.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

Follow the procedures in this section to upgrade the data warehouse schema to version 7.9.6.1 and migrate data.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following topics:

8.7.1.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1

  1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

  2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

  3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

8.7.1.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse

  1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

  2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

  3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

  4. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

  5. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_JDE_811SP1_812 and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

    If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_JDE_90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

  6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

  7. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

8.7.1.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully

  1. Validate the data in the upgraded data warehouse.

  2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

  3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:

    7961_UPGRADE_DROP_INDEXES.sql

    796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql

    7961_UPGRADE_PRE_DIMENSION.sql

    7961_UPGRADE_POST_SCRIPT.sql

  4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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 tables

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

8.7.2 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases

This section contains the following procedures:

8.7.2.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2

  1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

  2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

  3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

  4. Run the UPGRADE_7962.ctl script. Appendix E, "Using the DDLimp Utility to Run CTL Files."

  5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  6. Run the DDL_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

8.7.2.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse

  1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

  3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

  4. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

  5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

  6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

  7. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

8.7.2.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully

  1. Validate the data in the upgraded data warehouse.

  2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

  3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:

    dropallindexes.sql

    7962_UPGRADE_PRE_CTL_SCRIPT.sql

    7962_UPGRADE_PRE_DIMENSION.sql

    createETLIndexes.sql

    createQueryIndexes.sql

  4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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 tables

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

8.7.2.4 Resetting Refresh Dates

After verifying the data was migrated successfully into the upgraded data warehouse, follow this procedure to reset refresh dates.

  1. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE_811SP1_812 and execute the RESET_DAC_REFRESH_DATES workflow.

    If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE90 and execute the RESET_DAC_REFRESH_DATES workflow.

  2. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.

    In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

  3. In DAC, do the following:

    1. Navigate to the Setup view, and click the Physical Data Sources tab.

    2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

    3. Click the Refresh Dates subtab (in the lower pane).

    4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

  4. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

    1. In the Informatica Administrator, select the Upgrade repository service.

    2. In the General Properties area of the Properties tab, click Edit.

    3. Make sure the operating mode of the repository service is set to Exclusive.

    4. Click OK.

    5. Choose Actions, and then click Delete Contents.

    6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.7.3 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

8.7.3.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3

  1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

  2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

    Note: You must drop the query indexes before running the scripts to upgrade the schema.

  3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

  4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

  5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

8.7.3.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse

  1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

  4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

  5. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

  6. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.

    If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

  7. Upgrade geography-related attributes if necessary for your environment:

    1. Determine whether a geography-related upgrade is necessary by executing the following query:

      SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

    2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

      If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

  8. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

  9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

  10. Run the createQueryIndices script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

8.7.3.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully

  1. Validate the data in the upgraded data warehouse.

  2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

  3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:

    7963_UPGRADE_PRE_CTL_SCRIPT.sql

    7963_UPGRADE_PRE_DIMENSION.sql

    7963_UPGRADE_DROP_ETLINDICES.sql

    7963_UPGRADE CREATE_ETLINDICES.sql

    dropQueryIndices.sql

    createQueryIndices.sql

  4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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 tables

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

  6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

    1. In the Informatica Administrator, select the Upgrade repository service.

    2. In the General Properties area of the Properties tab, click Edit.

    3. Make sure the operating mode of the repository service is set to Exclusive.

    4. Click OK.

    5. Choose Actions, and then click Delete Contents.

    6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.8 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, follow the procedures in this section to upgrade from Oracle BI Applications version 7.9.6.1 and 7.9.6.2 to version 7.9.6.3.

This section includes the following topics:

8.8.1 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.2

Follow this procedure to upgrade from Oracle BI Applications version 7.9.6.1 to version 7.9.6.2 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database

  1. Execute the following scripts:

    • 7962_UPGRADE_TMP_TABLES.sql

    • 7963_UPGRADE_TMP_TABLES.sql

    1. Open the SQL client for your database type.

    2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

    3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

    4. Execute the script.

  2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

  3. Generate upgrade scripts from DAC.

    1. Log into DAC.

    2. From the menu bar, select Tools, then ETL Management, and then Configure.

    3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.

      The Configuration tab of the Data Warehouse Configuration Wizard is active.

    4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.

      The Data Warehouse SQL tab is active.

    5. Do the following:

      - Select the appropriate physical data source name for the Teradata database.

      - In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

      The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

      upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

      upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

      upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

      upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

    6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.

      ALTER TABLE <Table Name> ADD <Column Name><attributes>;

    7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

    8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

    9. Execute the scripts in the upgrade-regular.sql file.

    10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

    11. Recreate STATISTICS on any column on which they were dropped.

  4. Execute the following scripts:

    • 7962_UPDATE_DEFAULTS.sql

    • 7963_UPDATE_DEFAULTS.sql

  5. Execute the 7962_Backup_Tables.sql script.

  6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

  7. Configure the Informatica parameter file 7962_UPG_PARAMStxt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

  8. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE_811SP1_812 and execute the following workflows in the order specified:

    • UPGRADE_DIMENSIONS

    • UPGRADE_FACTS

    • RESET_DAC_REFRESH_DATES

  9. If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE90 and execute the following workflows in the order specified:

    • UPGRADE_DIMENSIONS

    • UPGRADE_FACTS

    • RESET_DAC_REFRESH_DATES

  10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

  11. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.

    In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

  12. In DAC, do the following:

    1. Navigate to the Setup view, and click the Physical Data Sources tab.

    2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

    3. Click the Refresh Dates subtab (in the lower pane).

    4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

  13. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

  14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

  15. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

  16. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

  17. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.

    If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

  18. Upgrade geography-related attributes if necessary for your environment:

    1. Determine whether a geography-related upgrade is necessary by executing the following query:

      SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

    2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

      If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

  19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

  20. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

    1. In the Informatica Administrator, select the Upgrade repository service.

    2. In the General Properties area of the Properties tab, click Edit.

    3. Make sure the operating mode of the repository service is set to Exclusive.

    4. Click OK.

    5. Choose Actions, and then click Delete Contents.

    6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.8.2 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.3

Follow this procedure to upgrade from Oracle BI Applications version 7.9.6.2 to version 7.9.6.3 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database

  1. Execute the following script:

    • 7963_UPGRADE_TMP_TABLES.sql

    1. Open the SQL client for your database type.

    2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

    3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

    4. Execute the script.

  2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

  3. Generate upgrade scripts from DAC.

    1. Log into DAC.

    2. From the menu bar, select Tools, then ETL Management, and then Configure.

    3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.

      The Configuration tab of the Data Warehouse Configuration Wizard is active.

    4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.

      The Data Warehouse SQL tab is active.

    5. Do the following:

      - Select the appropriate physical data source name for the Teradata database.

      - In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

      The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

      upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

      upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

      upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

      upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

    6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.

      ALTER TABLE <Table Name> ADD <Column Name><attributes>;

    7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

    8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

    9. Execute the scripts in the upgrade-regular.sql file.

    10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

    11. Recreate STATISTICS on any column on which they were dropped.

  4. Execute the following scripts:

    • 7963_UPDATE_DEFAULTS.sql

  5. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

  6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

  7. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

  8. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

  9. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.

    If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

  10. Upgrade geography-related attributes if necessary for your environment:

    1. Determine whether a geography-related upgrade is necessary by executing the following query:

      SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

    2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

      If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

  11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

  12. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.

    In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

  13. In DAC, do the following:

    1. Navigate to the Setup view, and click the Physical Data Sources tab.

    2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

    3. Click the Refresh Dates subtab (in the lower pane).

    4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

  14. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

    1. In the Informatica Administrator, select the Upgrade repository service.

    2. In the General Properties area of the Properties tab, click Edit.

    3. Make sure the operating mode of the repository service is set to Exclusive.

    4. Click OK.

    5. Choose Actions, and then click Delete Contents.

    6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.9 Localizing the Policy Store

The Oracle BI Applications 7.9.6.3 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English

  1. Stop the Oracle BI Services.

  2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.

    For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

  3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

  4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

  5. Start Oracle BI Services.

8.10 Importing the Oracle BI Applications Version 7.9.6.3 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.3 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.3 LDIF file

  1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

  2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

  3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

  4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

  5. Click Save.

8.11 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and presentation catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.3 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.3 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.3 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.3 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 8.9, "Localizing the Policy Store."

8.12 Merging Oracle BI Applications Version 7.9.6.3 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded the Oracle BI repository you are currently using and the standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading) to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.11, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

This process merges your customizations of a prior release of the Oracle BI repository with the new release 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:

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 8-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 8-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 $ORACLE_BI_HOME\biapps\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.

8.12.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade

  1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

    • Original

    • AfterEqualize

    • AfterMerge

    • AfterManualWork

    • AfterRegressions

  2. Copy the following repositories to 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.

8.12.2 Equalizing the Oracle BI Repositories

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 $ORACLE_BI_HOME\biapps\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.

    Table 8-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

    Table 8-2 Rename MAP Files to Be Used for Various Releases

    Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version) Rename MAP File to Be Used

    Siebel Business Analytics Applications 7.0.x

    Not available

    Siebel Business Analytics Applications 7.5.x

    Not available

    Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

    Rename77-7963.map

    Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

    Rename771-7963.map

    Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

    Rename782-7963.map

    Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

    Rename783-7963.map

    Oracle BI Applications 7.9.0

    Rename79x-7963.map

    Oracle BI Applications 7.9.1

    Rename79x-7963.map

    Oracle BI Applications 7.9.2

    Rename79x-7963.map

    Oracle BI Applications 7.9.3

    Rename793to7963.map

    Oracle BI Applications 7.9.4

    Rename794to7963.map

    Oracle BI Applications 7.9.5

    Rename79x-7963.map

    Oracle BI Applications 7.9.5.1

    Rename7951to7963.map

    Oracle BI Applications 7.9.5.2

    Rename7951to7963.map

    Oracle BI Applications 7.9.6

    Rename79x-7963.map

    Oracle BI Applications 7.9.6.2

    Not required

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository

  1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

  2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_793.rpd). An example of the equalizerpds command is as follows:

    equalizerpds -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 $ORACLE_BI_HOME\biapps\upgrade folder.

    If the equalizerpds.exe executable file runs correctly, no errors are returned.

  3. 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 -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
-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.

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

8.12.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

8.12.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories

  1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.

  2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

  3. From the Administration Tool menu bar, select File, then select Merge.

  4. Select the Merge Type option Full Repository Merge.

  5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).

  6. Enter the password for the original repository.

  7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

  8. Enter the password for the modified repository.

  9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.

    The new repository will contain the final results of the merge.

  10. Select the Equalize during merge check box.

  11. Click Next.

  12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

  13. To locate subsequent rows with empty Decision fields, click the Decision header cell.

    When all rows have a value in the Decision field, the Finish button is enabled.

  14. Select the Check consistency of the merged RPD check box.

  15. Click Finish.

    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.

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

  17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

8.13 Merging Oracle BI Applications Version 7.9.6.3 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.11, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

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 Fusion Middleware Upgrade Guide for Oracle Business Intelligence

8.13.1 Trimming the Input Presentation Catalog

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

8.13.2 Merging the Oracle BI Applications Version 7.9.6.3 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.11, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.3 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see Chapter 17, "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.3 presentation catalog with the current (custom) catalog

  1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.

    For instructions, see Section 17.4, "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

  2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.3 (out-of-the-box) presentation catalog in offline mode.

  3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.3 (out-of-the-box) presentation catalog.

    For instructions, see Section 17.6.1, "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

  4. If you created custom catalog groups that are not in the version 7.9.6.3 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.3 presentation catalog.

    To convert custom catalog groups to application roles, run the following command:

    runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

    For example:

    runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

    This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

    Note: If the specified replacement user or group is not already present in the presentation catal11g Release 1 (11.1.1)og already, then this operation will fail.

    For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

8.13.3 Testing the Results of the Presentation Catalog Upgrade

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.

8.14 Regression Testing the Oracle BI Repository Merge

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

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

  2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

  3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.

    For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

  4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

  5. Execute the edited logical SQL against the merged repository, and save the results.

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

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us