My Oracle Support Banner

Execution Errors in ODI 12c are Caused by the Parsing of <% %> Tags in Jython, Java or Groovy Comments (Doc ID 2356250.1)

Last updated on JULY 21, 2020

Applies to:

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

Symptoms

Oracle Data Integrator (ODI) 12c Knowledge Modules (KMs) and/or Procedures use Jython code, and some of them have comment lines.

If the comment line mentioned above refers to a substitution method that cannot be successfully parsed, ODI fails to execute the code.

The error message can vary depending on the substitution method in use.

For example, if the following comment is implemented in a Knowledge Module:

# Data Server no longer exists in the ODI topology. Hence commenting the following line.
# <%=odiRef.getFlexFieldValue("3010","1400","ODI_REP_URL")%>

... and a Data Server with internal ID 3010 does not exist in the ODI Topology...

... the execution of a mapping using this KM would fail, and the following message would be received:

The application script threw an exception: com.sunopsis.core.SnpsFlexFieldException: SnpConnect.getObjectByIdent : SnpConnect does not exist

Note the same behavior equally affects Java and Groovy comments.

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.