Analytics Software

Only repositories from versions of ODI 11.1.1.6.0 and above can be upgraded to ODI 12c.  If the scenario is one where we have to upgrade ODI 10g to ODI 12C, we must first upgrade ODI 10g to ODI 11.1.1.6.0 before performing the ODI 12c upgrade.

Please close this ticket if it has helped you.

Thanks for your help.

I understand we can upgrade the repository database from 11.1.0.7 to 12.1.0.2  but before upgrade the repository we need to upgrade the existing ODI component from 10.1.3.5.4 to 11.1.1.9.0 then we can upgrade the repository to 12c because 11.1.1.9.0 ODI component is compatible with 11.1.0.7. and 12.1.0.2 repository database. But I need to understand how the existing ODI maps migrate to new 12.1..0.2 environment.

Here’s the high-level background information that I have regarding ODI upgrade.

1.    Currently, we have Oracle 10g ODI components and an Oracle 11.1.0.7 repository running on a Linux server that resides in the Lift and Shift area at our Data Center. 

2.    One of the goals of this project is moving ODI environment off the existing Linux server because the server needs to be decommissioned.

3.    An additional goal is to upgrade ODI components and repository to Oracle 12c.

4.    We have worked with engineering to come up with a solution because ODI existing Linux server cannot be used.

a.    The solution provided by engineering will provide an ODI as-a-service environment that will run Oracle 12c ODI components and repository.  

5.    As I see it, we need to develop a plan to migrate existing ODI maps into the ODI aas environment and repository.  We do not need to build a new database.  Perhaps we will need a new schema in the existing repository.

6.    I believe we may need to upgrade existing ODI repository and components to higher versions of Oracle 11g prior to migrating them to the Oracle 12c ODI aas environment.

Thanks,

10g to 11g >>

Prerequisites:

Clone the ODI 10g master & work repositories

Move the Schema to the target instance

Install the ODI 11g on the target instance

Considerations

Make sure the cloned Work repository is named exactly the same as the original one

I will be explaining only about upgrading the Database repositories not the Middle tier portion will be covering in a different blog.

I had issues running the Upgrade Assistant on a 64 bit windows box – (you can give a try)

Both my ODI 10 g & 11g were running on Oracle Enterprise Database 11g

Note: Always run the UA on the Cloned repositories rather than directly on the Original 10g ODI

The Upgrade Assistant is present in the following directory ODI_HOME/bin

Prerequisites For An ODI 11g to ODI 12C upgrade >>

Clone

A clone should be made of each original master and work repository on 11g.   The Upgrade Assistant does not support repositories distributed on different instances of ODI. 

The ODI 12c version now uses unique IDs that follow the GUID convention. This avoids collision during the import of ODI objects and allows for simpler management and consolidation of multiple repositories within any given project.

Backup

Create a backup for each master and work repository (11g).  The backup will enable administrators to restore to the initial (pre-upgrade) state, if necessary.

Support

Before the upgrade of schemas, make sure the database supports the newer version.  (Note: ODI 12c supports database versions 11.2.0.3 R2 and above.)

Version Upgrade

Only repositories from versions of ODI 11.1.1.6.0 and above can be upgraded to ODI 12c.  If the scenario is one where we have to upgrade ODI 10g to ODI 12C, we must first upgrade ODI 10g to ODI 11.1.1.6.0 before performing the ODI 12c upgrade.

After successfully installing ODI 12c using the odi_121200.jar file, Opatch needs to be applied from the odi_1212_opatopatch.rar file available from the same folder downloaded from Oracle Technology Network (OTN).

Before running a Opatch, shut down all Oracle and ODI services.

Call the OPtach.bat file available in <Oracle_Home>\OPatch directory

“opatch napply <download_folder>\odi_1212_opatch”

Thanks SaQ-Orcl for your help to achieve my goal!

I have one more senario. Could you please also help me there.

1. ODI component is running on 10.1.3.5.4 with repository database 11.1.0.7. Both are running on same server.

2. Upgrade the ODI component from 10.1.3.5.4 to 11.1.1.9.0 with repository database 11.1.0.7. Both will reside on same server.

3. Upgrade and Migrate the Repository Database from 11.1.0.7 to 12.1.0.2 and Migrate to different server but ODI component(11.1.1.9.0) still remain on old server.

4. Upgrade ODI Component from 11.1.1.9.0 to 12.2.1.2.6 and migrate from old server to new server(This is separate server than the Repository server). Means both ODI Components and Repository Database reside on separate servers.

So my question is around step 3. How to perform repository database upgrade and migrate while other ODI Components remain on old version and old server? Actually I am new to ODI and trying to understand how ODI work.

Thanks again for help me on this.

Hi,

you can do it. ODI componenet reside in domain and componenet require for studio are stores in Repo. so you need to reconfigure your ODI.

https://docs.oracle.com/cd/E23943_01/upgrade.1111/e12642/tasklist.htm#ODIUG152

1) export10g ODI repository schemas in DMP files

example : my 10g schemas are "ODI_MASTER" and "ODI_WORK"

     exp userid=odi_master/*odi_master* file=c:\odi_master10g.dmp

     exp userid=odi_work/*odi_work* file c:\odi_work10g.dmp

2) import the dump file into new schemas in the new database (or is it the same database ? in my case, it was a different one)

exampe : I clone them in "ODI_MASTER_10g" and "ODI_WORK_10g"

     imp userid=SYSTEM/password touser=*odi_master_10g* fromuser=odi_master file=c:\odi_master10g.dmp

     imp userid= SYSTEM/password touser=*odi_work_10g* fromuser=odi_work file=c:\odi_work10g.dmp

But, in order to solve the bug I've mentionned before, I also import the work repository in a schema with the SAME NAME than the original

     imp userid= SYSTEM/password touser=*odi_work* fromuser=odi_work file=c:\odi_work10g.dmp

(in my case, I've 2 different database : one for ODI 10g and one for ODI 11G)

3) Install 11g ODI (without repository creation)

4) Launch the Upgrade Assistant : "ua.bat". You need to have a variable JAVA_HOME declared in windows.

- during the step 2, choose the second option with the 3 box

- during the migration processus, give the connexion information about the cloned master schema (odi_master_10g)

- then give the password of the "odi_work_10g" OR, if it's not possible (bug ?) the "odi_work"

- wait until the end of the migration

5) Launch ODI 11g Studio

- create a new login connected to the schema "odi_master_10g" (it has been converted properly in 11g, now)

- choose the associated work ref detected by ODI

- use the supervisor login (then create new user/admin login with security module if you want)

6) Connect with this new login

- check if your projects anre models are here

- check if your topology is right

Please close this thread by marking correct if it has helped you.

Thanks SaQ-Orcl for explaining this. I am still confuse with Migration and Upgrade the 11g database to 12c database with ODI repository schema to different server.

Here is the confusion.

Suppose Currently we are running on ODI 11.1.1.9.0 with Database 11.1.0.7 on same server and we want to Migrate only the Repository Database to different server and during the migration we also want to upgrade the database to 12.1.0.2. I have checked that ODI 11.1.1.9.0 is compatible with both 11.1.0.7 and 12.1.0.2 databases so database versions are compatible.  So my question is how we can Migrate and Upgrade the database on the same time from 11.1.0.7 to 12.1.0.2 on different server while the ODI 11.1.1.9.0 remain on old server?  What steps needs to perform for such task?

I am thinking about the following steps. Please let me know these are correct or not.

1. Install empty 12.1.0.2 repository database on new server

2. Export the existing 11.1.0.7 ODI repository schema and import into 12.1.0.2 database on new server

3. backup the existing 11.1.0.7 ODI repository Schema in case of failure.

4. Connect to the ODI 11.1.1.9.0 Studio and modify all repository connection parameters to point to the new database.

Yes, you can go with steps you mentioned.