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 JUNE 16, 2022

Applies to:

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


When executing a mapping or procedure 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.


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 (like variable name, project name, column name, etc), represent a fictitious sample. Any similarity to actual environments, past or present, is purely coincidental and not intended in any manner.


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

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