How To Move The OBIA and ODI 11g Repositories To a New RDBMS Instance or Schema (Doc ID 2109247.1)

Last updated on NOVEMBER 17, 2016

Applies to:

Business Intelligence Applications Consumer - Version 11.1.1.8.1 and later
Information in this document applies to any platform.

Goal

Having the database and BI Application servers, both running on the same machine. Now planning to move the database to a new server or a new instance or a new schema. The goal is to point the existing BI Apps to the new DB target.

The process requires a full and working installation of BI Apps in the original machine/DB/schema. From now on called 'Source Server'

  1. Have a complete Installation of BIAPPS in Source Server.
  2. Need to move only the schemas to another server. From now on called 'Destination Server'.
  3. WLS Installation will remain on Source Server.

 

Very important:

The solution process below in no means pretends to be used for migration processes already in place by OBIA documentation and articles. This is NOT the purpose of this document, but to solve those cases where for some reason the working OBIA environment is being moved. Please notice that an actual "migration" involves many other steps when it is needed to migrate from TEST to PROD, for example.

 

Good Practices for Performance:

The process should only move OBIA Components IO schema, OBIA Components Repository schema, and ODI Repositories schema. The OBIA DW schema should "always" remain on the same server where the ODI Agent is for performance purposes. When the Agent populates the target, it better not have to use the Network anymore, and if the DW is also moved, then the Agent should move with it.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms