Although the Entry Does Exist in SCHEMA_VERSION_REGISTRY, the ODI 12c Upgrade Assistant Fails with "Entry for ODI does not exist in SCHEMA_VERSION_REGISTRY" Error
(Doc ID 2810648.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Data Integrator - Version 12.1.2.0.0 and laterInformation in this document applies to any platform.
Symptoms
The Upgrade Assistant (UA) fails upgrading Oracle Data Integrator (ODI) Repositories, and the following error is received:
Note that the SCHEMA_VERSION_REGISTRY view is fully accessible to the SYSDBA or non-SYSDBA user running the UA, and the ODI Repository entry has been manually created in the <DB SCHEMA>.SCHEMA_VERSION_REGISTRY$ table, using the following INSERT SQL command:
insert into <DB SCHEMA>.SCHEMA_VERSION_REGISTRY$
( comp_id, comp_name,
mrc_name, mr_name, mr_type,
owner,
version,
status,
upgraded,
start_time, modified, edition )
values
( 'ODI',' Master and Work Repository',
'<SOME VALUE>', 'ODI_REPO' ,'ODI_REPO',
'<Owner value which has some lower-case or mixed-case letters>',
'12.2.1.3.0'
'VALID',
'N',NULL,NULL,NULL ) ;
commit ;
The issue can be reproduced at will with the following steps:
- Insert the record into SYSTEM.SCHEMA_VERSION_REGISTRY. Pay attention to use the same case letter for the data inserted into the OWNER table column.
- Run the UA, and observe the error.
Cause
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
Symptoms |
Cause |
Solution |
References |