Essbase load from ODI fails with: com.hyperion.odi.essbase.ODIEssbaseException: Error Records Reached The Maximum Error Threshold : 1


When running a load to Essbase from ODI the load fails and the following is seen in the ODI Operator log:

com.hyperion.odi.essbase.ODIEssbaseException: Error records reached the maximum error threshold : 1
at com.hyperion.odi.essbase.ODIEssbaseDataWriter.loadData(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
at org.python.core.PyMethod.__call__(PyMethod.java)
at org.python.core.PyObject.__call__(PyObject.java)
at org.python.core.PyInstance.invoke(PyInstance.java)
at org.python.pycode._pyx15.f$0(<string>:23)
at org.python.pycode._pyx15.call_function(<string>)
at org.python.core.PyTableCode.call(PyTableCode.java)
at org.python.core.PyCode.call(PyCode.java)
at org.python.core.Py.runCode(Py.java)
at org.python.core.Py.exec(Py.java)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
at com

 

 

In cases like this it is usually pretty simple to determine the root cause of the failure if you enable error logging on the Essbase IKM in your ODI interface as per note 1088139.1.

This will generate a log containing the errors returned from Essbase. The errors are usually pretty explicit about the root cause of the issue. Errors like these are commonly associated with missing metadata in the Essbase target. The log entries are in csv (comma separated) format so you can import the csv into a spreadsheet such as Microsoft Excel and the error will be in the final column. If the error mentions a missing member then the column header shows the dimension name so usually allows you to see which dimension the member is in.

It can sometimes be helpful when debugging to temporarily increase the value of the MAXIMUM_ERRORS_ALLOWED option of the Essbase IKM in ODI so that you can see more of the errors which are being produced (if multiple errors seem to be being produced) so that you do not need to correct problems one at a time (for potentially hundreds of failures or more).

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s