Upgrading ODI 11.1.1.5 Repositories to ODI 11.1.1.6

Upgrading ODI 11.1.1.5 Repositories to ODI 11.1.1.6:

Today we will upgrade existing ODI 11.1.1.5 repositories to 11.1.1.6. First take the backup of existing repositories. Open SQL Developer and move on as per below screenshot.
I am copying my master repository to ODI_MASTER2.



Similarly you can take backup for all your repository. Once backup is done we have to call the upgrade assistant.
1st go to the ODI_HOME\bin location of 11.1.1.6. In my case it is C:\oracle\product\11.1.1\Oracle_ODI_1\bin. So in command prompt, switch to that location and call ua.bat as given in below screenshot and proceed accordingly.







That’s all. Now you can use your repositories for 11.1.1.6. One thing I noticed that the same repositories can be used in 11.1.1.5. If you want to configure local agent refer  this post and for Java EE Agent  this one.

Comments are always welcome 🙂 .

About Bhabani 86 Articles
Bhabani has 10 plus years of experience in Data warehousing and Analytics projects that has span across multiple domains like Travel, Banking and Financial, Betting and Gaming Industries. Solution areas he focuses on designing the data warehouse and integrating it with cloud platforms like AWS or GCP. He is also a Elite level contributor at OTN forum more than 9 years. He loves to do experiment and POC on different integration tools and services. Some of his favorite skills are Redshift, Big Query, Python, Apache Airflow, Kafka, HDFS, Map Reduce ,HIVE, Habse, Sqoop, Drill, Impala.

50 Comments

  1. Dear Bhabani,

    it seems that you have got the same screenshot used multiple times. Step welcome is shown five times. Could you fix this?

    Cheers
    JL

  2. Thank you!

    Very nice article, by the way. We are doing the same right now. Although i haven’t found the aequivalentof the sql developer schema copy function for our db2 database 🙂

    Continue your good work 🙂

    My best wishes

    Jan

  3. Hello Bhabani,

    do you happen to know, if the username (in your example: odi_master2) must correspond 1 to 1 to the schema name?
    I would like to provide odim as a user, but have db schema odim_116 upgraded. Would that be possible?

    Cheers
    Jan

  4. Hi ,

    I have already ODI 11.1.1.5 installation ,means i need to re unistall and install 11.1.1.6 and then do the upgrade asistatnt(ua.bat) Is thi sright?

  5. Hi Bhabani,
    Thank you for your post.. We are trying to migrate from ODI 10G to ODI 11G.. I followed the step above and migrated successfully, but we are getting the following error while i am creating new connection in “Repository Connection Information”
    oracle.odi.core.config.MasterRepositoryVersionMismatchException: ODI-10179: Client requires a repository with version 04.03.04.02 but the repository version found is 4.2.02.01.
    at oracle.odi.core.repository.Repository.getMasterRepository(Repository.java:118)
    at oracle.odi.core.OdiInstance.createMasterRepository(OdiInstance.java:491)
    at oracle.odi.core.OdiInstance.(OdiInstance.java:544)
    at oracle.odi.core.OdiInstance.createInstance(OdiInstance.java:521)
    at com.sunopsis.graphical.dialog.SnpsDialogLoginDetail.testConnection(SnpsDialogLoginDetail.java:755)
    at com.sunopsis.graphical.dialog.SnpsDialogLoginDetail.access$4(SnpsDialogLoginDetail.java:743)
    .
    .
    .
    Any idea about this error..Appreciated your reply..
    Many Thanks,
    Subbu

    • Might be you are using the backup repository connection details. Please double check if you are using the newly migrated credentials or not.
      Run this in ODI master repository schema to get the master repository version
      select rep_name ,rep_version,rep_type from snp_loc_rep ;

      Run this in ODI work repository schema to get the work repository version
      select rep_name ,rep_version,rep_type from snp_loc_repw;

      Thanks
      Keep visiting.

  6. Dear Bhabani,
    Thanks for your reply.. we are trying to migrate from production to development, i copied schema to development database server, everything was fine without any error but i checked the repository version, it is showing 4.2.02.01 which is old one..i think it is not migrated properly.. .whether i have to follow any other steps for migrating from production to development ?
    Many thanks,
    Subbu

    • Hi Subbu,
      I have never tried this (prod to dev). Also if your production schema is in execution mode and dev schema is development mode then i doubt you can do it..Better you take backup for all repository and try R&D on this. As i stated above in my post is the process to upgrade the repository i dont think there is something else need to be done. Just keep in mind all repository should be in same version.

      • Dear Bhabani,
        Thank you for your reply..It was successful after I updated database connection string in SNP_MTXT_PART table, i migrated successfully from production to development..

        Many thanks,
        Subbu

        • Hi Subbu,

          I would like to know the entry you had made in the SNP_MTXT_PART table. Currently the table does not have any data in it? I am facing the same issue of “Client requires different version”.

          Would appreciate any information.

          Arun

          • Hi Subbu,

            Can you please share what you have updated exactly in SNP_MTXT_PART? You did that after migrating and in the 11g database, correct?

            I’m facing the same issue you had…

            Thanks in advance.

            Cheers,
            Jose Vieira

          • Hi subbu, i am having the similar issue too. Can you send me what entry you had made in the SNP_MTXT_PART table

  7. Hi,
    could you pls explain about the RCC which should be checked after the installation whether all the steps are succeeded or not.

    • Hi Kasturi,
      RCC generally used prior to the upgradation. Please look into the Article ID 1058107.1 for more details.

      The Repository Consistency Checker (RCC) is an Oracle Data Integrator (ODI) utility developed by the ODI Support team to:

      Verify the structure and data integrity of your ODI Repositories in order to guarantee their successful upgrade to ODI 10.1.3.6 or above.

      Detect Repository data issues, such as:
      1. Incoherent or inconsistent Internal Identifiers.
      2. Damaged, duplicate and orphan Texts.
      3. Corrupted and orphan Log messages.
      4. Integration Interfaces which are not in ad-equation with the Topology.
      5. Incorrect interactions between design objects.

      It is highly recommended to run the RCC utility:

      1. Prior to upgrading Repositories to a version compatible with ODI 10.1.3.6 or above.
      (Note if your upgrade requires intermediate steps (such as, for example, an upgrade from Sunopsis v3 to ODI 11g, which requires an intermediate upgrade from Sunopsis v3 to ODI 10g, then from ODI 10g to ODI11g), you should run the RCC prior to the first upgrade operation (in the above example, run the RCC on the Sunopsis v3 Repositories).)
      2. To diagnose Repository data corruptions and inconsistencies.
      3. Regularly for Work Repositories hosted in a Microsoft SQL Server database with multiple concurrent developers.

      Known limitations
      The Repository Consistency Checker (RCC) utility runs on Windows Operating System only.

      Check this link to find out the compatibility
      http://dwteam.in/wp-content/uploads/2013/02/rcc.jpg

      • Thank you so much Bhabani…..!
        One more suggestion needed.
        Actually mine is a cluster prod environment.
        That means the Master and Slave kind of thng.
        When master is down, then the slave should start working automatically.
        At this situation, could u pls tell me the sequence of steps to be followed for the migration from ODI 10g to ODI 11.1.1.6.3

        Thanks in very advance

        • Hi Kasthuri,
          I have never done the migration in a RAC environment. Better log into oracle support to get the documentation on it. You can refer this doc aswell.
          http://docs.oracle.com/cd/E25054_01/core.1111/e10106/odi.htm#BGBGJGGA
          Best on the above link what i found is that the master/work repository creation seems to be the normal way we do. So probably the upgradation will be same like asusual. But better to get a clarification from oracle support team on this.
          Let me know in case of any issues.
          Thanks
          Bhabani

          • Hi Bhabani,

            Can you pls tell what is the latest RCC version for checking ODI10g repositories and how to download it?

            Only a DBA can download it or anyone can do it?

            Many thanks.

          • Hi Kasthuri,
            You can only donwload it from oracle support. After login search for the id 1058107.1 where you can find the pre-requisites and download link. I believe the help of dba is not required right here if you have the necessary privileges as mentioned. But if you think the repository is quite big please consult your dba.

            Thanks
            Bhabani

  8. Hi Bhabani,
    I have referred the id you have provided for RCC.
    Very useful. Got everything there. Thanks.
    Also pls suggest the patch for the upgrade from ODI 11.1.1.6.0 to ODI 11.1.1.6.3

    Many thanks in advance
    Kasthuri

    • Please refer the id 456313.1 ( scroll down there, you can see it.) . You can download the path from there. I also noticed the latest patch available for 11.1.1.6.4

      Thanks
      Bhabani

  9. Hi Bhabani,
    Could you pls tell me that the RCU (Repository Creation Utility) is mandatory for the migration of ODI from 10g to 11g.

    Thanks

  10. Hi Bhabani,
    Could you pls tell me how to find the grants and privileges on a particular table in oracle 11g.

    DBA_TAB_PRIVS is not helping because i don have sys privilege.

    Thanks in Advance

  11. Hi Bhabani,
    Could u pls tell me how to get a function definition by using a oracle query.

    Early response would be appreciable

    Thanks in Advanccce

  12. Hi Bhabani,
    Could you pls tell me, is it possible creating more than one Master repository connection for the same instance.

    When i try to do so, am getting the below error while configuring the work repository details in topology manager.

    “A work repository already exists for this connection.
    Enter the repository password to declare it in your Master Repository”

    I tried with both the new master and work repository password. But no luck.

    Could you pls advice.

    • 1.You can always create one master repository for one user. Similarly you can create one work repository for one user. Note that you can create multiple work repository which can be linked to only one master repository but not vicevarsa.
      2. Also you can take one user for both master repository and work repository. This is not a good idea (because all table will messup) i believe but the behavior of RCU is in the same way. Thats why i like to create repository directly from odistudio instead of RCU.

      Bhabani

  13. Hi,
    While executing the RCC, am getting an error like the below.
    ‘Failed to connect to the RCC Master Repository. Verify that the ODI Repository Consistency Checker environment is up and running’
    I configured the master repo details in sample.properties as mentioned in the oracle article
    Could you pls suggest where am doing mistake.
    Thanks

  14. Hi Bhabani,
    After successful upgrade, need to execute the patch p14037855_111163_Generic for bringing ODI from ODI 11.1.1.6.0 to 11.1.1.6.3

    Could you please share the article id which has the documentation about this patch.

    Thanks in advance

  15. Getting the following error while trying to establish connection to the master repo We have installed, 11.1.1.7 version of ODI on the local PC :-
    oracle.odi.core.config.MasterRepositoryVersionMismatchException: ODI-10179: Client requires a repository with version 04.03.04.02 but the repository version found is 4.2.02.01.

    Please advise which version of ODI studio should we install to make this work.

    Thank you.
    RK

  16. We tried the above process , but it shows the Repository registry update is succeded but Oracle Data Integrator upgarde failed. Please guide.

  17. I am new to this… and we are planing to upgrade our environment (ODI 10g to ODI 11g). Apart from mentioned steps above do we need to take care any other Tasks.
    My main point is … any code related things can taken care (if I am not wrong)…

    Please kindly let me know. Thanks.

  18. Hi,if I have ODI 11.1.1.3, wherein I have 5 schemas (1 RCU run and the rest 4 created using create user command in db) with one schema for Master and the rest for Work Repo. Will the upgrade process upgrade the 4 work repo schemas? FYI.. these tables do not showup in schema_version_registry table with COMP_ID. OR is it that I will need the 4 schemas as RCU run schemas?
    Regards,
    Suraj.

  19. Hi,

    I have upgraded odi existing repositories from 11.1.5.0 to 11.1.1.6.0.i was able to connect to upgraded work repositories from new master repo.

    Now query is,i have created new work repository under same master repository.
    But the error as below:

    oracle.odi.core.config.WorkRepositoryVersionMismatchException: ODI-10179: Client requires a repository with version 04.03.04.02 but the repository version found is 04.03.03.08.

    Do i need to upgrade this repository or any work around is there?

    Advance thanks for your reply.

    Regards
    Archana

  20. Hi, few months ago I can see all screenshots correctly but now I can’t see them? Is it posible to see them back?
    Thank you!
    Regards

  21. we have our ODI repositories(10g) on X oracle DB and using which the ODI nighty ETL loads the data to Y oracle DB. Now are looking to upgrade the ODI from 10g to 11g first and then from 11g to 12c by moving the repositories from “X” to “Z” so the installation and upgrade assistant should be installed on “Z”(new) server where new oracle database also resides with minimum version of (11.1.1.6)right? and After the upgrade we connect to work and master reps using the clients(designer and operator)?

Leave a Reply

Your email address will not be published.


*