Oracle BI Applications Upgrade - Part 2

as promised in part 1 of this series, here is part 2 of a summary of steps for an Oracle BI Applications upgrade:

Step 5: Import the DAC 7.9.5 repository

Use the DAC 7.9.5 client to create a second connection to a new schema and create an empty DAC repository.
Import the BI Apps 7.9.5 DAC repository into the new schema using the DAC client.

Note: you can not import the 7.9.5 DAC repository using DAC 10.1.3.4 (see below).

Optional Step: Install DAC 10.1.3.4

The Data Warehouse Administration Console 10.1.3.4 has been released some time ago.
This is an optional step. You can stick with the DAC that comes with Oracle BI Applications 7.9.5 but you might want to look at the new features of DAC 10.1.3.4. However, if you decide to use the new DAC, there is no easy way to revert back (the DAC repository) to 7.9.5, so a good reason to start with taking a backup.

Use the new DAC to create connections to the old and new repository and allow DAC 10.1.3.4 to upgrade the schema by logging in to both connections.


Quick delta for DAC 7.9.5 to 10.1.3.4

  • No hibernate libraries required, but make sure you copy the database connectivity .jar file into the lib directory
  • Must create authentication file on first login, then change the Administrator password. For subsequent logins, use the Administrator account.
  • Existing repository (7.9.x) is automatically upgraded to new DAC version upon first login, you can not use earlier DAC versions (this applies to both client and server) after the upgrade
Step 6: Upgrade and merge the Informatica Repository

Upgrade the old version of the Informatica Repository following the instructions in the Informatica PowerCenter 8.1.1 Installation and Configuration Guide. The process is executed in the web-based Administration Console.



Next you can establish connections to both repositories (the one you customized and the new one) in Informatica Repository Manager. You can now compare folders or objects and copy the custom folders to the new repository. If you adhered to the recommendation to do all modifications in custom folders, this is a very safe path. If you made any customizations to objects in standard folders, you most probably have to reapply these changes to the objects in the new repository.


Step 7: Upgrade the OBAW Schema

According to the OBI Apps 7.9.5 Upgrade Guide you have to

  • run prepared SQL scripts
  • use the ddlimp utility to change the schema
  • start some specialized workflows manually, if you upgraded the Siebel source application to 8.0 or 8.1
  • Reset the sequence generators of Informatica using a script
  • Import a specialized repository which contains upgrade workflows and run the respective workflows
Need a break? All right, see you in a few days for the final. In part 3 we will discuss merging the DAC repository, running test execution plans, upgrade and merge the .rpd file and the presentation catalog.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

The intention of this blog is to share findings about Siebel CRM and Oracle Business Intelligence Enterprise Edition (Oracle BI EE formerly known as Siebel Analytics) from technical and other (sometimes unprecedented) perspectives.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today