My Oracle Support Banner

Smart Import Causes Some Schemas to No Longer be Mapped in ODI Context (Doc ID 2647705.1)

Last updated on MARCH 17, 2020

Applies to:

Oracle Data Integrator - Version 11.1.1.9.0 to 12.2.1.3.190708 [Release 11gR1 to 12c]
Information in this document applies to any platform.

Symptoms

During the import of objects in Oracle Data Integrator (ODI) 11g or ODI 12c, whether in the Studio or with the SDK, sometimes the reference to physical schemas in the contexts is lost.

It is also observed that the export file contains all Contexts, and not just the Contexts used by the Interfaces / Mappings exported.

Expected result:

  1. Only the Context that is used by the Interface / Mapping should be exported / imported.
  2. Import should not result in lost references between Context and Physical Schema.

To reproduce:

  1. Have an environment with many Contexts.
      
  2. Make sure that all Contexts are associated with a Physical Schema.
      
  3. Export an Interface / Mapping that uses one Context.
    Notice that the export file contains all Contexts, not only the one used by the Interface / Mapping.
      
  4. Smart import into the same ODI Work Repository.
    Notice that some Contexts are no longer mapped / associated to a Physical Schema.

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


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