My Oracle Support Banner

Column Data Types Are Not Defined During External Table Creation When Executing An ODI 12c Reusable Mapping (Doc ID 2278320.1)

Last updated on JULY 04, 2017

Applies to:

Oracle Data Integrator - Version 12.1.2.0.0 to 12.2.1.2.0 [Release 12c]
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Information in this document applies to any platform.

Symptoms

A Temporary Interface in Oracle Data Integrator (ODI) 11g uses a knowledge module that calls the getColList() substitution method with a SOURCE_CRE_DT pattern to create an external table:

create external table <%=snpRef.getTargetTable( "TABLE_NAME")%>_ext
(
<%=odiRef.getColList("", "\t[COL_NAME]\t[SOURCE_CRE_DT] ", ",\n", "", "")%>
)

The execution of the Temporary Integration Interface in ODI 11g correctly generates the column datatypes.

For example:

create external table MY_TABLE_ext
(
  COL1 CHAR(2) ,
  COL2 TIMESTAMP ,
  COL3 CHAR(2) ,
  COL4 INTEGER ,
  ...
)

After upgrading the above to ODI 12c, the columns datatypes are no longer generated in the Reusable Mapping lines of code:

create external table MY_TABLE_ext
(
  COL1 ,
  COL2 ,
  COL3 ,
  COL4 ,
  ...
)

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.