Skip to main content
Blog

Essential Steps for a Smooth Transition to ODI 12c from ODI11g

When upgrading ODI repositories from version 11g to 12c, it’s not uncommon to encounter an issue where the upgrade process appears to be stuck at a certain percentage. This situation typically arises when certain conditions are not met.

Here are some of the points to ensure before upgrading the repositories to minimize the risk of failure:

  • Optimize the upgrade process by minimizing the size of cloned work repositories. Achieve this by archiving execution logs to reduce unnecessary data. It can simply be done by clicking on purge logs in ODI studio. In one case,this reduced the schema size by 16GB.
  • Connect to all the work repositories, delete any duplicate objects like variable names, package names, procedures etc (the older version allowed objects with same name).
  • Grant unlimited tablespace to the master and work repository schemas
    Alter user <master_repo> quota unlimited tablespace to <master_repo_users>;
    Alter user <work_repo> quota unlimited tablespace to <work_repo_tbspc>;
  • Add multiple data files to the work repository schema
    ALTER TABLESPACE your_tablespace_name ADD DATAFILE ‘/path/to/datafile1.dbf’ SIZE 1024M,
    ‘/path/to/datafile2.dbf’ SIZE 1024M,
    ‘/path/to/datafile3.dbf’ SIZE 1024M;
  • Enable “Auto Extend”, auto-extend for the specified data file, allowing it to extend automatically in increments of 100 megabytes, with a maximum size of unlimited
    ALTER DATABASE DATAFILE ‘/path/to/your/datafile.dbf’ AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;
  • Ensure there is enough disk space, processor, memory to run the upgrade
  • Ensure at the time of upgrade no major activity like backup, export or import of schema is running on the DB as it takes precedence and may slow down the process 
  • Review the work repositories, remove unwanted projects, interfaces that are duplicates, delete the interfaces that do not open or corrupted.
  • Ensure the master repository is pointing to the destination work repository and not the source from where it was migrated.  (Most common mistake hence upgrade fails)
    1. Open the migrated master repository via 11g ODI Studio 
    2. Go to master repository > Topology > Work Repositories > Select the work repositories > Click on the “switch” like symbol > JDBC
  • Update this JDBC string to the destination DB JDBC string  > Save. 
  1. Repeat the #b if you have more than one repository.
  2. If the upgrade failed but the repositories show already 12c version then update the schema_version_registry, reimport the 11g schemas, follow all the above steps and run the upgrade again. 

Leave a Reply