My Oracle Support Banner

ODI Does Not Reverse Engineer Foreign Key After Datastore Table Is Renamed (Doc ID 2713968.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle Data Integrator - Version 12.2.1.4.200304 to 12.2.1.4.201011 [Release 12c]
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200304 to 12.2.1.4.201011
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 12.2.1.4, when a table in one datastore references a table in another datastore with a foreign key (FK), changing the name of the datastore results in a reverse-engineer that is missing that foreign key.

For example:

  1. There is one data server with two physical schemas called SchemaA and SchemaB.
  2. For SchemaA, the model ModelA is created. After, datastore TableA that contains a primary key is reversed-engineered.
  3. TableA is renamed to TableAX.
  4. For the second physical schema, SchemaB, model ModelB is created. Here, the datastore TableB needs to be reversed-engineered so that it has a foreign key pointing to TableA.
  5. The TableB is reversed-engineered, however, the foreign key pointing to the renamed TableAX does not appear.

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.