My Oracle Support Banner

ODI 12c No Longer Parses Variables if the Name is Not Prefixed by the Project Code or GLOBAL Scope (#GLOBAL.VAR Versus #VAR) (Doc ID 2405415.1)

Last updated on JUNE 08, 2018

Applies to:

Oracle Data Integrator - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 11g, Variables could be referred to without specifying their Project or Global scope. For example, using '#VAR' instead of '#GLOBAL.VAR'.

The same code no longer functions post upgrade to ODI 12c. Variables used in Knowledge Module (KM) steps are not parsed or substituted to a value if the scope is not mentioned (#GLOBAL.VAR must be used instead of #VAR).

Example of code implemented in the KM Code generated by ODI 11g Code generated by ODI 12c
repdriver = '#VAR' repdriver = '#GLOBAL.VAR' repdriver = '#GLOBAL.VAR'
loadoutname = "#VAR.out" loadoutname = "#GLOBAL.VAR.out" loadoutname = "#VAR.out"
#loadcmdfile = "#VAR.ldcmd" #loadcmdfile = "#GLOBAL,VAR.ldcmd" #loadcmdfile = "#VAR.ldcmd"

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.