How To Change The JDBC Connecting String For The OBIEE 11g Metadata Repository "RCU" Database Without Starting WebLogic / AdminServer
(Doc ID 1424665.1)
Last updated on MAY 02, 2018
Applies to:Business Intelligence Suite Enterprise Edition - Version 184.108.40.206.0  to 220.127.116.11.161018 [Release 11g]
Information in this document applies to any platform.
This document explains how to modify the JDBC connections to the metadata repository database where the OBIEE 11g schemas are stored as installed via the Repository Creation Utility (RCU).
There are internal dependancies you may mis with an ad-hoc export/import
This document pertains to changes to the underlying database that contains the schemas, not moving the schemas.
For Disaster Recovery see:
Oracle Fusion Middleware Disaster Recovery Guide11g Release 1 (11.1.1) -- Part Number E15250-03
3.3 Database Considerations
Sample scenario or business use case:
The OBIEE MDS and BIPLATFORM Schemas were created via the Repository Creation Utility (RCU) on an Oracle RAC database with 3 instances / nodes.
When OBIEE was installed, the Database Connect String specified for the BIPLATFORM and MDS schemas was in the Oracle Database / RAC format for example:
The requirement now is for OBIEE to access the BIPLATFORM and MDS schemas only via instance / node 3 of the Oracle RAC database/
The original installation connection screen is configured as Node 1, Node 2, Node 3.
The failover for the RAC nodes is configured on the server-side.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document