My Oracle Support Banner

Incorrect Mapping Aliases Are Observed AT SQL Generation Time After Migrating To ODI 12.1.3 (Doc ID 1992549.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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

Symptoms

After migrating from Oracle Data Integrator (ODI) 12.1.2.0.x to ODI 12.1.3.0.0, at Mapping SQL generation time incorrect Aliases for a sub-select clause are observed:

SELECT
LKP_USER_AGENT_LKP_USER_AG_2.DEVICE DEVICE ,
LKP_USER_AGENT_LKP_USER_AG_2.RANK_NO RANK_NO ,
LKP_USER_AGENT_LKP_USER_AG_2.OS_VERSION OS_VERSION ,
LKP_USER_AGENT_LKP_USER_AG_2.LOOKUP_NK LOOKUP_NK ,
LKP_USER_AGENT_LKP_USER_AG_2.SOURCE_CODE SOURCE_CODE
FROM
(
...) LKP_USER_AGENT_LKP_USER_AGEN_4                                   
(LKP_USER_AGENT_LKP_USER_AG_2.LOOKUP_NK = 'AMAZON_TABLET_STORE'
AND LKP_USER_AGENT_LKP_USER_AG_2.RANK_NO = 1
AND LKP_USER_AGENT_LKP_USER_AG_2.SOURCE_CODE = 'AMAZON_TABLET'
)

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!


In this Document
Symptoms
Changes
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.