Oracle BI Applications Upgrade - Part 3

Welcome back, these are the final steps in an Oracle BI Applications upgrade scenario

Step 8: Merge the DAC repository

After merging the custom folders in the Informatica repository, we have to merge the second (of four) repositories, that is the DAC repository. The new DAC 10.1.3.4 has the unique feature of allowing direct upgrades and merge processes of two existing repositories, even from Siebel Analytics Applications 7.8.4, which had a "non-partioned" repository without containers. Please note that the following steps can only be executed in DAC 10.1.3.4. Previous versions do not support an automated upgrade.

Below is a short summary of steps, please see the documentation for more details:

• Connect to the new standard DAC repository and export the containers you want to upgrade.
• Connect to the old, customized DAC repository and start the upgrade wizard.
• Select Refresh Base. This option is recommended when you upgrade from BI Applications 7.9.x
• Inspect the difference report and resolve conflicts if necessary
• Click Merge

The result is a DAC repository which inherits the modifications made to the standard containers between 7.9.x and 7.9.5 as well as the custom container. However, there might be some additional manual work necessary to complete the DAC upgrade.

Step 9: Run test Execution Plans

After verifying the Setup view of DAC (registering Informatica servers for 8.1.1 is different) you can rebuild your execution plans and execute test runs to ensure that the ETL works as expected.

Step 10: Upgrade and merge the Oracle BI rpd file

Number 3...

If you have customized the Oracle BI rpd file and you want to benefit from changes made by the Oracle developers, you have to use the equalizerpds utility and the Administration Tool in order to accomplish a merge of the three versions

• Prior Customer Repository
• Prior Standard Repository
• New Standard Repository

into a single New Customer Repository

According to the Oracle BI Applications 7.9.5 Upgrade Guide you have to get the original 7.9.x rpd file from the Upgrade folder and copy it to a temporary folder along with your customized rpd and the new standard rpd

You then execute the following major steps

• use equalizerpds.exe to resolve minor differences in spelling (such as "Core"."W_DAY_D" is the same as "Core"."W Day D"
• Compare repositories to find which elements have been created, removed or modified
• Merge the repositories using the Administration Tools 3-way merge functionality
• Test the outcome of the merge

Step 11: Upgrade the Oracle BI Presentation Catalog

If you need to combine the changes of Oracle engineering with your customizations (in order to benefit from the new standard list formats for Siebel Marketing, for example) you have to merge the different versions of BI Presentation Catalogs into one. This is supported by the Catalog Manager tool. You have the choice between a simple copy and paste process if you adhered to the best practice of creating your own folders and the merge functionality of Catalog Manager.

Conclusion

Adhering to best practices and staying "close to the standard" during the development phase is crucial for successful and timely upgrades. Oracle BI Applications get you in touch with 4 different architectures and repositories (Informatica, DAC, rpd and presentation catalog) all of which exist in an original standard, a customized and a new standard version.

These are the recommended ways to customize them:

• Informatica: Only modify objects in custom folders
• DAC: Only modify objects in the custom container
• rpd: Trim the original repository and create new presentation catalogs if needed
• Presentation Catalog: Only modify objects in custom folders

Have a nice day