My Oracle Support Banner

How To Implement a Solution for ODI Work Internal Repository ID Collision (Doc ID 424680.1)

Last updated on NOVEMBER 03, 2023

Applies to:

Oracle Data Integrator - Version to [Release 4.1.01 to 11gR1]
Information in this document applies to any platform.


When copying developments from an Oracle Data Integrator (ODI) Work Repository into an other one which has the same ID, problems are signaled at import time:

ODI-10013: This import action has been canceled because it could damage your repository.
This is due to an SNP_XXX object that has object identifier <myID> that is greater than that for the current SNP_XXX id sequence.
Importing this object would lead to primary key violations in the future.

    == or ==


com.sunopsis.core.q: This import action has been cancelled because it could damage your repository (problem with the identifier sequences)

    == or ==

ODI-10093: You are importing an object from another repository with the same identifier. It is forbidden.




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
 Step 1. Backup the database.
 Step 2. Re-compute the table/index statistics, and re-size the storage space.
 Step 3. Purge the ODI log.
 Step 4. Apply the ODI patches required for the renumbering to succeed.
 Step 5. Run the RCC to determine the list of internal IDs already in use.
 Step 6. Chose a new Repository ID value.
 Step 7. Renumber the objects IDs, and change the Repository internal ID.
 ODI and later.
 ODI 10g, Sunopsis v4 and Sunopsis v3.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.