Change Internal ID of ODI Repository

Change Internal ID of ODI Repository:

Hi Guys!!
I have a quick post on renumbering the internal id of ODI repositories. Please take backup of your repositories before attempting below steps. Otherwise you might lose your valuable projects.

Change Internal ID of ODI Repository

Right click on the work repository and click renumber

repository_renum2

 

Click Yes.

repository_renum3

repository_renum4

 

Provide the new ID.

repository_renum5

repository_renum6

 

Click Yes.

repository_renum7

repository_renum8

repository_renum9

 

You are done!!.

Thank you for reading.

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.

5 Comments

  1. Hello Bhabani,

    I tried changing internal id of my repository, but all the times, appears the message: “ODI-23044: The new ID you have chosen is already in use as a table “SNP_VAR_DATA” primary key. The renumbering has been aborted. No changes have been made.”
    I deleted the register at the table SNP_VAR_DATA that was using the number and the problem goes on. Do you have any idea?

    Thanks!

    • Renato, I encountered the “The new ID you have chosen is already in use” error. I simply changed the new ID to a high number (900) and I got past that error. Unfortunately, now I’m getting a new error: “ORA-02292: integrity constraint (ODI_MASTER_REP_V7B.FK_VERSION_SNP_DAT) violated – child record found”.

      I’m currently upgrading ODI. I think I will leave my repository ID alone in Dev and just try to change the IDs in the upper environments.

  2. Hi Renato,

    I have the same problem, with some id´s i´ve got to start the renumbering process but failed with no specific error, could you resolve your problem?

    Thank you.

  3. Hello when I am trying to connect to Work repository I am getting the error can you please let me know the issue

    oracle.odi.core.config.RepositoriesNotBoundException: ODI-10150: Work repository with ID 10 is not bound to master:
    Definition in master ID:10, Name:DEV_WORKREP10, Timestamp:1461075568213
    Definition in work ID:10, Name:DEV_WORKREP10, Timestamp:1500404903422.

  4. Hi,
    Does this solution work for packages also?
    I have duplicated one package and made the changes in the duplicate. Now I am having internal id conflict during deployment

Leave a Reply

Your email address will not be published.


*