What Fixes are Required for the Renumbering of ODI 11g Repositories to Succeed?
(Doc ID 2337048.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Data Integrator - Version 126.96.36.199.0 to 188.8.131.52.99 [Release 11gR1]
Information in this document applies to any platform.
A renumbering of Oracle Data Integrator (ODI) Repositories is always required for resolving conflicts around object IDs when import operations are performed.
The ODI 11g Developer's Guide at https://docs.oracle.com/middleware/11119/odi/develop/toc.htm, provides the appropriate guidance:
Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator
> 3 Administering the Oracle Data Integrator Repositories
> 3.8 Advanced Actions for Administering Repositories
> 3.8.3 Renumbering Repositories
There are however a couple of identified issues that prevent the Master and/or Work Repository renumbering from succeeding:
Document 1461397.1 - Unable To Renumber A Work Repository In ODI 11g Due To Error New ID Already In Table "SNP_VAR_DATA"
Document 1588351.1 - Unable To Renumber A Work Repository In ODI 11g Due To "ODI-23044: The new ID you have chosen is already in use" In Tables "SNP_SCEN_TASK" or "SNP_SESS_TASK"
Document 2320283.1 - Renumbering of ODI 11g Master Repository Fails Due to Incorrect Renumbering of I_METH in SNP_METHOD Table
Document 1497522.1 - "The new ID you have chosen is already in use..." Signaled When Attempting To Renumber An ODI Repository
The purpose of this document is to provide the list of fixes required for achieving the renumbering of ODI 11g Repositories.
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
|Questions and Answers|
|Patches required for the renumbering of ODI Master Repository to succeed|
|Patches required for the renumbering of ODI Work Repository to succeed|