FDMEE 11.2.x - ODI Step COMM Init Process Fails With Error "ImportError: No Module Named Logging"
(Doc ID 3001993.1)
Last updated on FEBRUARY 06, 2024
Applies to:
Hyperion Financial Data Quality Management, Enterprise Edition - Version 11.2.9.0.000 and laterInformation in this document applies to any platform.
Symptoms
When trying to run a Data Load Rule or a batch or a System Maintenance script, the process just hangs.
When checking in ODI Studio, it fails at the step Name "COMM Init process"
ERROR
-----------------------
FROM ODI STUDIO -
ODI-1226: Step COMM Init Process fails after 1 attempt(s).
ODI-1232: Procedure COMM Init Process execution fails.
ODI-1590: The execution of the script failed.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "", line 22, in
ImportError: No module named logging
at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:396)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:247)
at oracle.odi.runtime.agent.execution.interpreter.SessionTaskScriptingInterpretor.scripting(SessionTaskScriptingInterpretor.java:190)
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 |