ODI 12.2.1 Mapping Execution Error "ODIEssbaseException: The source column [<NAME_>] is not valid for dimension"
(Doc ID 2391198.1)
Last updated on MAY 26, 2023
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]Oracle Data Integrator Cloud Service - Version 17.1.3 to 17.1.3
Information in this document applies to any platform.
Symptoms
Executing an Oracle Data Integrator (ODI) mapping between Oracle Database and Essbase results in the following error message (or similar) in the session log:
ODI-1590: The execution of the script failed.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last): File "", line 78, in
at com.hyperion.odi.essbase.ODIEssbaseMetaReader.validateSourceMetadata(Unknown Source)
at com.hyperion.odi.essbase.ODIEssbaseMetaReader.validateExtractOptions(Unknown Source)
at com.hyperion.odi.essbase.AbstractEssbaseReader.beginExtract(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: The source column [<NAME_>] is not valid for dimension [<NAME>].
In the above example, the string '<NAME>' has already been added as an Essbase reserved keyword in ODI.
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! |