Although a "Target Load Order" Is Defined in the ODI 12c Mapping "Logical" Design, the Target Datastores Are not Updated in the Desired Order (Doc ID 2757064.1)

Last updated on JULY 30, 2024

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.

Goal

An Oracle Data Integrator (ODI) 12c Mapping is configured to load data into several different target Datastores. For example: <TARGET1>, <TARGET2>, <TARGET3> and <TARGET4>

The desired "Target Load Order" has been defined in a Mapping "Logical" tab, however ODI appears to ignore them.

Looking into the Mapping "Physical" design, the way the flow is defined causes parallel loads of data into two of the targets, and only the two other ones are executed in sequence.

What causes ODI to ignore the "Target Load Order" defined?
How to re-design the flow, so that the correct phases are shown on the Mapping "Physical" tab?

Solution

	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.

Although a "Target Load Order" Is Defined in the ODI 12c Mapping "Logical" Design, the Target Datastores Are not Updated in the Desired Order (Doc ID 2757064.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!