My Oracle Support Banner

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 JUNE 07, 2023

Applies to:

Oracle Data Integrator - Version 12.1.2.0.0 and later
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200123 and later
Information 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:

  1. 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.
  2. Run the UA, and observe the error.

Changes

 

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!


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