Saturday, October 12, 2013

How to install OBIEE 11g Without RCU

OBIEE installation Without RCU.

I have several posts in OTN , How  to install OBIEE 11g Without RCU? I found one workaround option but it would be suitable in production/UAT environments.

One of the prerequisites of installing OBIEE 11g is, the installation of two repository schema into a database.

1.      BIPLATFORM : This schema will store Scheduler Tables , Usage Tracking Tables etc..
2.      MDS:  'MDS'  (Metadata Service) is also required for OBIEE installation.

See the tables in below Screen:

These repository schema are created using RCU (Repository  Creation Utility). According to Oracle documentation, this is a required step. During the course of installation, RCU warrants a user with "SYSDBA" privileges to,
v  Create the repository schema accounts and 
v  create new table spaces  or map the existing table spaces to the new schema
v  Grant certain roles and privileges required by the schema. 
In Production environments Bank/Industries organizations have strictly restricted against using accounts with SYSDBA privileges.

Follow the below Steps:

 There is a way to get the repositories installed on to the target database without invoking RCU. This solution requires,
  • A local database (or, the database where you have control/privileges to create table spaces) 
  • Creation of repositories by running RCU on the local database and 
  • Exporting the repositories to the target database.
Please remember, this activity requires coordination and support from DBA team. The entire activity is transparent and should cause little or or no resistance from them to participate.

The installation activity is as follows,
  1. Create two table spaces on the local database (or the database where you have control/privileges to create table spaces) for RCU schema. 
  2. Install repository schema using RCU.
  3. Export the two repository schema.
  4. Note table space name and the schema owner (BIPLATFORM and MDS) names.
  5. Create table spaces and two users, with exact same name, on the target database (This is critical, Oracle uses these exact names)
  6. Grant following system privileges,
    • Connect, Resource, Create Sequence to BIPLATFORM and MDS 
    • Execute privileges on "DBMS_LOCK" to BIPLATFORM
    • Execute on ""DBMS_LOB" to MDS
  7. Use the export dump created earlier to import the data into the schema in the target database, created above.
  8. Following objects need recompilation,
    • procedure:"obi_biplatform"."sddeletestudy"
    •  procedure:"obi_biplatform"."sdcommitstudy"
    • procedure:"obi_biplatform"."sdgetlearningdata"
    • procedure:"obi_biplatform"."sdgetlearningidrange"
    • procedure:"obi_biplatform"."sdlearningmappingcleanup"
  9. Additionally RCU also creates two entries in the "SYSTEM.SCHEMA_VERSION_REGISTRY" table. Review these entries in your local database and create them in the target database.
  10. Grant select on this table to BIPLATFORM and MDS schema.
Your two repositories are successfully recreated on your target database. You can now safely install OBIEE target server. 

Satya Ranki Reddy

No comments:

Post a Comment