How To Move The OBIA and ODI 11g Repositories To a New RDBMS Instance or Schema
(Doc ID 2109247.1)
Last updated on SEPTEMBER 28, 2023
Applies to:
Business Intelligence Applications Consumer - Version 11.1.1.8.1 and laterInformation 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'. Be sure to keep the old databases for Repository & DW up and running. (Don’t shut those old databases down as WebLogic will get confused and will throw errors pointing to database being down when trying to “Activate Changes” after hitting “Save” when making the Connection Pool settings changes below).
- Have a complete Installation of BIAPPS in Source Server.
- Need to move only the schemas to another server. From now on called 'Destination Server'.
- WLS Installation will remain on Source Server.
Very important:
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
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
Goal |
Solution |
References |