My Oracle Support Banner

Wrong Source used by ODI when a Variable is Named the Same as a Target Column (Doc ID 2406432.1)

Last updated on MAY 24, 2019

Applies to:

Oracle Data Integrator - Version 12.1.2.0.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

When executing a mapping in Oracle Data Integrator (ODI) which transfers data to a target table that has a column with the same name as a variable (global or local), ODI will incorrectly generate SQL code using the variable name instead of the source column.

For example, when there is a variable named "SAMPLE_REF_CODE" that matches the name of the target column, the source will be replaced with the variable reference instead of the mapped source column.

INSERT INTO <DBSCHEMA>.C$_TARGET (
     SAMPLE_REF_CODE
)
VALUES(
     :SAMPLE_PROJECT.SAMPLE_REF_CODE
)

This issue occurs when using a Loading Knowledge Module (LKM) based on the binding mechanism (on step "Insert new rows"), such as "LKM SQL to Oracle (Built-In)" or "LKM SQL to SQL (Built-In)".

NOTE: In the example given any details, ie the port configured, represent a fictitious sample. Any similarity to actual configurations, persons, living or dead, is purely coincidental and not intended in any manner.

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.