| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Version 7.9.6.2 Part Number E17801-01 |
|
|
View PDF |
| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Version 7.9.6.2 Part Number E17801-01 |
|
|
View PDF |
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/technology/about/index.html.This section contains instructions for upgrading Oracle BI Applications when you are running Oracle EBS as your source system.
This section includes the following topics:
Section 6.3, "Upgrading to Informatica PowerCenter Version 8.6.1 and Hotfix 11"
Section 6.7, "Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"
Section 6.8, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"
Section 6.10, "Upgrading the Oracle BI Presentation Catalog"
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 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 Installation Guide for Informatica PowerCenter Users.
Note the following points:
Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.
Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.
If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)
You must install Informatica PowerCenter 8.6.1 and Hotfix 11 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 8.6.1 differ significantly from PowerCenter 7.x versions. Oracle recommends that you carefully review the Informatica PowerCenter 8.6.1 documentation, which is included on the Informatica DVD provided with Oracle BI Applications.
For a summary of installation instructions for installing Informatica PowerCenter 8.6.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 8.6.1, refer to the Informatica PowerCenter Installation Guide, Informatica PowerCenter Configuration Guide, Informatica PowerCenter Administrator Guide, and related documentation.
For information about applying Hotfix 11, see PowerCenter Version 8.6.1 Hotfix 11 Release Notes. This PDF is included with the Informatica documentation on the Informatica PowerCenter DVD and is also included with the Hotfix 11 installation.
To upgrade to Informatica PowerCenter 8.6.1
Perform the pre-upgrade steps documented in the Informatica PowerCenter Installation Guide.
Install Informatica PowerCenter version 8.6.1 and Hotfix 11 by following the instructions in the Informatica PowerCenter Installation Guide and PowerCenter Version 8.6.1 HotFix 11 Release Notes.
Perform the post-upgrade steps documented in the Informatica PowerCenter Installation Guide.
Note the following points:
The Informatica PowerCenter 8.6.1 installation process includes upgrading your current Informatica Repository to the version 8.6.1 format. This process is necessary so that you will be able to access your current repository using version 8.6.1 client tools and so that you can perform the procedure Section 6.4, "Upgrading the Informatica Repository."
In Section 6.4, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository (for example, 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.
If you install Informatica PowerCenter 8.6.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch the Informatica Administration Console, select the Integration Service from the Navigator, click the Processes tab, click Edit, and enter the appropriate value for $PMRootDir.
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 8: Managing the Repository," in the Informatica PowerCenter Administrator Guide, which is included on the Informatica DVD provided with Oracle BI Applications.
To upgrade the Informatica Repository
Make sure you have backed up and renamed your current Informatica Repository.
Note:
This repository must be upgraded to the version 8.6.1 format during the procedure in Section 6.3, "Upgrading to Informatica PowerCenter Version 8.6.1 and Hotfix 11." You must upgrade this repository to the version 8.6.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 <PowerCenter_Installation_Directory>\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 6.2, "Upgrading Oracle BI Applications."Restore the Oracle_BI_DW_Base.rep repository into an empty schema.
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.
Informatica PowerCenter version 8.6.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:
Copying Source Files and Lookup Files
Setting PowerCenter Integration Services Relaxed Code Page Validation
Setting PowerCenter Integration Services Custom Properties
Creating the Repository Administrator User in the Native Security Domain
This section includes information you must follow to upgrade and configure DAC.
This section includes the following topics:
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 metatdata 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 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.2.
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.
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.
This section contains the following topics:
Section 6.7.1, "Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases"
Section 6.7.2, "Upgrading the Data Warehouse Schema from Version 7.9.x to 7.9.3 and Migrating Data"
Section 6.7.3, "Upgrading the Data Warehouse Schema from Version 7.9.3 to 7.9.4 and Migrating Data"
Section 6.7.4, "Upgrading the Data Warehouse Schema from Version 7.9.4 to 7.9.5. and Migrating Data"
Section 6.7.7, "Upgrading the Data Warehouse Schema from Version 7.9.6 to 7.9.6.1 and Migrating Data" (Applicable only if you are using an Oracle database as your data warehouse database.)
If you are currently running Oracle BI Applications release 7.9.0, 7.9.1 or 7.9.2, you need to perform the procedures in Section 6.7.1, Section 6.7.2, Section 6.7.3, Section 6.7.4, Section 6.7.5, Section 6.7.6, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.3, you need to perform the procedures in Section 6.7.1, Section 6.7.3, Section 6.7.4, Section 6.7.5, Section 6.7.6, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.4, you need to perform the procedures in Section 6.7.1, Section 6.7.4, Section 6.7.5, and Section 6.7.6, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.5, you need to perform the procedures in Section 6.7.1 and Section 6.7.5, and Section 6.7.6, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.5.1, you need to perform the procedures in Section 6.7.1 and Section 6.7.6, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.6, you need to perform the procedures in Section 6.7.1 and Section 6.7.7, and Section 6.7.8.
If you are currently running Oracle BI Applications release 7.9.6.1, you need to perform the procedures in Section 6.7.1 and Section 6.7.8.
These procedures add new tables, columns, and indexes to the existing data warehouse schema. They also modify the existing data warehouse schema objects.
The steps in this procedure are required for upgrading to Oracle BI Applications release 7.9.6.2 from all previous releases.
To perform common data warehouse upgrade steps
If you are using a DB2 database, you need to execute the stored procedure siebproc.sql, which creates procedures and functions needed by the DDLimp utility. This file is located in \dwrep\siebproc\db2udb.
Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <PowerCenter_Installation_Directory>\server\infa_shared\LkpFiles.
Restore the Upgrade repository:
Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <PowerCenter_Installation_Directory>\server\infa_shared\Backup.
Launch the Informatica PowerCenter Administration Console and restore Upgrade.rep (located in <PowerCenter_Installation_Directory>\server\infa_shared\Backup).
In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:
For the OLTP connection:
If you are using the Oracle EBS 11i source system, edit the connection PARAM_OLTP_ORA11i.
If you are using a Oracle EBS R12, R12.1.1, or R12.1.2 source system, edit the connection PARAM_OLTP_ORAR12.
For the OLAP connection, edit the connection PARAM_OLAP.
For the DAC database connection, edit the connection PARAM_DAC.
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.
Perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1 or 7.9.2.
To upgrade the data warehouse schema and migrate data into the upgraded data warehouse
Run the UPGRADE_793.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the ddl_793.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 793_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Migrate data into the upgraded data warehouse.
Configure the Informatica parameter file 793_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 793_UPG_PARAMS.txt."
In Informatica Workflow Manager, navigate to the folder UPGRADE_790_to_793 and run the Update_Dimensions workflow, and then run the Update_Facts workflow.
If you are using the Oracle EBS 11.5.10 source system, navigate to the folder UPGRADE_790_to_793_ORA11510, and run the SIL_PurchaseAmount_Patch workflow.
Verify the data migrated successfully.
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\SessLogs directory indicate errors or failures.
Check whether the script 793_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 scripts ddl_793.ctl and UPGRADE_793.ctl, 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 tablesIf 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.
Perform the procedure in this section to upgrade from Oracle BI Applications release 7.9.3 to 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. For instructions, see Appendix E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Run the 794_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Run the UPGRADE_794.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the ddl_794.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 794_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Migrate data into the upgraded data warehouse.
Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt.".
In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Verify the data migrated successfully.
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\SessLogs directory indicate errors or failures.
Check whether the script 794_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 scripts ddl_794 and UpgradPGRADE_794.ctl, 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 tablesIf 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 base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.4 to 7.9.5.
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. For instructions, see Appendix E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Run the UPGRADE_795.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the ddl_795.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Migrate data into the upgraded data warehouse.
Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Verify the data migrated successfully.
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\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 scripts ddl_795.ctl and UPGRADE_795.ctl, 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 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.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.5 to 7.9.5.1.
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. For instructions, see Appendix E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Run the 7951_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Run the UPGRADE_7951.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the ddl_7951.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 7951_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Migrate data into the upgraded data warehouse:
Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Verify the data migrated successfully.
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\Sesslogs directory indicates errors or failures.
Check whether the script 7951_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 scripts ddl_7951.ctl and Upgrade_7951.ctl, 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 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.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.5.1 to 7.9.6.1.
This section includes the following procedures:
Section 6.7.6.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"
Section 6.7.6.2, "Migrating Data into the Upgraded Data Warehouse"
Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.
Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.
To upgrade the data warehouse schema to version 7.9.6.1
If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.
Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.
Execute the script.
If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.
Execute the script.
If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.
Run the UPGRADE_796.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:
Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.
Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.
If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.
Execute the script.
Run the ddl_7961.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Follow this procedure to migrate data into the upgraded data warehouse.
To migrate data into the upgraded data warehouse
Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.
To verify the data migrated successfully
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\Sesslogs directory indicates errors or failures.
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
7961_UPGRADE_PRE_CTL_SCRIPT.sql
796_UPGRADE_PRE_DIMENSION.sql
796_UPGRADE_POST_SCRIPT.sql
7961_UPGRADE_POST_SCRIPT.sq
Check the log files for the ddl_7961.ctl and Upgrade_796.ctl scripts 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.
After verifying the data was migrated successfully into the upgraded data warehouse, follow this procedure to reset refresh dates.
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_TO_796_ORA11i and execute the RESET_DAC_REFRESH_DATES workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_TO_796_ORAR12 and execute the RESET_DAC_REFRESH_DATES workflow.
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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.
Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6 to release 7.9.6.1.
Note:
This procedure is applicable only if you are using an Oracle database for your data warehouse database.This section includes the following procedures:
Section 6.7.7.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"
Section 6.7.7.2, "Migrating Data into the Upgraded Data Warehouse"
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
Run the 7961_UPGRADE_DROP_INDEXES.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.
Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.
Execute the script.
Run the UPGRADE_7961.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.
Run the ddl_7961.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Follow this procedure to migrate data into the upgraded data warehouse.
To migrate data into the upgraded data warehouse
Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.
Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.
To verify the data migrated successfully
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\Sesslogs directory indicates errors or failures.
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
7961_UPGRADE_PRE_CTL_SCRIPT.sql
7961_UPGRADE_PRE_DIMENSION.sql
7961_UPGRADE_POST_SCRIPT.sql
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 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.
Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.1 to 7.9.6.2.
This section contains the following procedures:
Section 6.7.8.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"
Section 6.7.8.2, "Migrating Data into the Upgraded Data Warehouse"
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
Generate the scripts to drop and create indexes. For instructions, see Section C.1, "Generating Scripts to Drop and Create Indexes."
Run the script to drop all indexes. For instructions, see Section C.2, "Running the Script to Drop All Indexes."
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.
Run the UPGRADE_7962.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files."
Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Run the DDL_7962.ctl script. For instructions, see Appendix F, "Using the DDLimp Utility to Run CTL Files.".
Follow this procedure to migrate data into the upgraded data warehouse.
To migrate data into the upgraded data warehouse
Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
Run the script to create ETL indexes. For instructions, see Section C.3, "Running the Scripts to Create ETL and Query Indexes."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Run the script to create Query indexes. For instructions, see Section C.3, "Running the Scripts to Create ETL and Query Indexes."
Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.
To verify the data migrated successfully
Check whether any of the Informatica mapping log files stored in the <PowerCenter_Installation_Directory>\server\infa_shared\Sesslogs directory indicates errors or failures.
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
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 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.
If your data warehouse database platform is Teradata, you can upgrade to Oracle BI Applications version 7.9.6.1 from Oracle BI Applications 7.9.x.
This section includes the following topics:
Section 6.8.1, "Upgrading Oracle BI Applications from Version 7.9.0 to 7.9.6.2"
Section 6.8.2, "Upgrading Oracle BI Applications from Version 7.9.3 to 7.9.6.2"
Section 6.8.3, "Upgrading Oracle BI Applications from Version 7.9.4 to 7.9.6.2"
Section 6.8.4, "Upgrading Oracle BI Applications from Version 7.9.5 to 7.9.6.2"
Section 6.8.5, "Upgrading Oracle BI Applications from Version 7.9.5.1 to 7.9.6.2"
Section 6.8.6, "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.0 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
Execute the following scripts:
793_UPGRADE_TMP_TABLES.sql
794_UPGRADE_TMP_TABLES.sql
795_UPGRADE_TMP_TABLES.sql
7951_UPGRADE_TMP_TABLES.sql
7961_UPGRADE_TMP_TABLES.sql
7962_UPGRADE_TMP_TABLES.sql
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.
Execute the script.
Edit and execute the 793_RENAME_AND_EXCEPTIONS.sql script.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the 793_RENAME_AND_EXCEPTIONS.sql script.
Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;
For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.
For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.
Execute the 793_RENAME_AND_EXCEPTIONS.sql script.
Recreate STATISTICS on any column on which they were dropped.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the following scripts:
794_UPDATE_DEFAULTS.sql
795_UPDATE_DEFAULTS.sql
7951_UPDATE_DEFAULTS.sql
7961_UPDATE_DEFAULTS.sql
7962_UPDATE_DEFAULTS.sql
Execute the 793_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 793_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 793_UPG_PARAMS.txt."
In Informatica Workflow Manager, navigate to the folder UPGRADE_790_to_793 and run the Update_Dimensions workflow, and then run the Update_Facts workflow.
If you are using the Oracle EBS 11.5.10 source system, navigate to the folder UPGRADE_790_to_793_ORA11510, and run the SIL_PurchaseAmount_Patch workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 794_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."
In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute the UPGRADE_DIMENSIONS and UPGRADE_FACTS workflows.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 795_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7951_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 796_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7961_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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).
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
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.
Follow this procedure to upgrade from Oracle BI Applications version 7.9.3 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
Execute the following scripts:
794_UPGRADE_TMP_TABLES.sql
795_UPGRADE_TMP_TABLES.sql
7951_UPGRADE_TMP_TABLES.sql
7961_UPGRADE_TMP_TABLES.sql
7962_UPGRADE_TMP_TABLES.sql
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.
Execute the script.
Edit and execute the 794_RENAME_AND_EXCEPTIONS.sql script.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the 794_RENAME_AND_EXCEPTIONS.sql script.
Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;
For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.
For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.
Execute the 794_RENAME_AND_EXCEPTIONS.sql script.
Recreate STATISTICS on any column on which they were dropped.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the following scripts:
794_UPDATE_DEFAULTS.sql
795_UPDATE_DEFAULTS.sql
7951_UPDATE_DEFAULTS.sql
7961_UPDATE_DEFAULTS.sql
7962_UPDATE_DEFAULTS.sql
Execute the 794_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."
In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 795_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7951_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 796_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7961_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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.
Follow this procedure to upgrade from Oracle BI Applications version 7.9.4 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
Execute the following scripts:
795_UPGRADE_TMP_TABLES.sql
7951_UPGRADE_TMP_TABLES.sql
7961_UPGRADE_TMP_TABLES.sql
7962_UPGRADE_TMP_TABLES.sql
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.
Execute the script.
Edit and execute the 795_RENAME_AND_EXCEPTIONS.sql script.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the 795_RENAME_AND_EXCEPTIONS.sql script.
Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;
For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.
For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.
Execute the 795_RENAME_AND_EXCEPTIONS.sql script.
Recreate STATISTICS on any column on which they were dropped.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the following scripts:
795_UPDATE_DEFAULTS.sql
7951_UPDATE_DEFAULTS.sql
7961_UPDATE_DEFAULTS.sql
7962_UPDATE_DEFAULTS.sql
Execute the 795_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7951_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 796_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7961_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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.
Follow this procedure to upgrade from Oracle BI Applications version 7.9.5 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
Execute the following scripts:
7951_UPGRADE_TMP_TABLES.sql
7961_UPGRADE_TMP_TABLES.sql
7962_UPGRADE_TMP_TABLES.sql
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.
Execute the script.
Edit and execute the 7951_RENAME_AND_EXCEPTIONS.sql script.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the 7951_RENAME_AND_EXCEPTIONS.sql script.
Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;
For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.
For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.
Execute the 7951_RENAME_AND_EXCEPTIONS.sql script.
Recreate STATISTICS on any column on which they were dropped.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the following scripts:
7951_UPDATE_DEFAULTS.sql
7961_UPDATE_DEFAULTS.sql
7962_UPDATE_DEFAULTS.sql
Execute the 7951_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 796_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7961_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt.
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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)
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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.
Follow this procedure to upgrade from Oracle BI Applications version 7.9.5.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
Execute the following scripts:
7961_UPGRADE_TMP_TABLES.sql
7962_UPGRADE_TMP_TABLES.sql
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.
Execute the script.
Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Open the 7961_RENAME_AND_EXCEPTIONS.sql script.
Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;
For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.
For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.
Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.
Recreate STATISTICS on any column on which they were dropped.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the following scripts:
7961_UPDATE_DEFAULTS.sql
7962_UPDATE_DEFAULTS.sql
Execute the 796_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for All Source Systems."
If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Additional Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."
If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section B.1, "Configuring Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."
If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section B.3, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."
If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section B.2, "Configuring Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
RESET_DAC_REFRESH_DATES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
Execute the 7961_Backup Tables.sql script.
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 E, "Running the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository."
Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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.
Follow this procedure to upgrade from Oracle Business 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
Execute the 7962_UPGRADE_TMP_TABLES.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.
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.
Generate upgrade scripts from DAC.
Log into DAC.
From the menu bar, select Tools, then ETL Management, and then Configure.
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.
Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.
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.
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>;
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.
For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.
Execute the scripts in the upgrade-regular.sql file.
Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.
Recreate STATISTICS on any column on which they were dropped.
Execute the 7962_UPDATE_DEFAULTS.sql script.
Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.
Configure the Informatica parameter file 7962_UPG_PARAMS.txt. Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."
If you are upgrading Oracle Financial Analytics, do the following:
Configure application-specific parameters and update mappings. For instructions, see Appendix B, "Configuring Parameters for Oracle Financial Analytics."
Make sure specific indexes are created. For instructions, see Appendix D, "Creating Indexes for Oracle Financial Analytics."
If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix B, "Configuring the COGS Fact Mapping for Oracle EBS R12."
If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS.
In DAC, do the following:
Navigate to the Setup view, and click the Physical Data Sources tab.
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.)
Click the Refresh Dates subtab (in the lower pane).
Query for the following tables, and, for each table, set the value in the Refresh Date column to NULL:
W_POSITION_D
W_POSITION_DS
W_POSITION_DH
FND_LOOKUP_VALUES
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 E, "Running the reset_infa_seq_gen.bat File on the Base Informatica Repository."
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.
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:
Section 6.9.1, "Preparing for the Oracle BI Repository Upgrade"
Section 6.9.5, "Regression Testing the Oracle BI Repository Merge"
The tasks in this section refer to multiple releases of the Oracle BI repository. Table 6-1 provides the names and descriptions of the repositories used in the examples in this section.
Table 6-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.
Table 6-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.
Table 6-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-7962.map |
|
Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0) |
Rename771-7962.map |
|
Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release |
Rename782-7962.map |
|
Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release |
Rename783-7962.map |
|
Oracle BI Applications 7.9.0 |
Rename79x-7962.map |
|
Oracle BI Applications 7.9.1 |
Rename79x-7962.map |
|
Oracle BI Applications 7.9.2 |
Rename79x-7962.map |
|
Oracle BI Applications 7.9.3 |
Rename793to7962.map |
|
Oracle BI Applications 7.9.4 |
Rename794to7962.map |
|
Oracle BI Applications 7.9.5 |
Rename79x-7962.map |
|
Oracle BI Applications 7.9.5.1 |
Rename7951to7962.map |
|
Oracle BI Applications 7.9.5.2 |
Rename7951to7962.map |
|
Oracle BI Applications 7.9.6 |
Rename79x-7962.map |
|
Oracle BI Applications 7.9.6.2 |
Not available |
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_793.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 6.10.2, "Upgrading the Oracle BI Presentation Catalog to a Newer Version"
Section 6.10.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.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|