My Oracle Support Banner

In ODI Mapping Editor, Physical Schema and Data Server Values Are Not Refreshed for Datastore if a Different Component Context Is Selected (Doc ID 2864009.1)

Last updated on AUGUST 31, 2023

Applies to:

Oracle Data Integrator - Version 12.2.1.4.220112 and later
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200123 and later
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) Mapping editor, when selecting a different Component Context (Forced) for the Datastore, Physical schema and Data server values are not refreshed and remain the same.
For example, In ODI Topology create multiple contexts and map a logical schema to a different physical schema for each context.

1. Create a Model for this logical schema.
2. Create or reverse Datastore for this model.
3. Create a mapping using those Datastore.
4. Click on a Datastore component on the mapping and below 3 properties are displayed:

-Component Context (Forced)
-Physical Schema
-Data Server

If a different context is selected in the drop down list of "Component Context (Forced)", the physical schema and data server remain the same.

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.