10 Replies Latest reply on Mar 21, 2016 1:18 PM by Las071214

    ODI Warning

    Las071214

      Hi,

      We have an interface which loads data from SQL to Essbase cube.IKM SQL to Hyperion Essbase(DATA)-Mindstream is the KM.
      Filter is set so that no data is loaded to Essbase.
      Below is the warning we are getting. We want to fix this warning.
      ODI version: 11.1.1.5. Please suggest. Thank You!

       

      org.apache.bsf.BSFException: exception from Jython:
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
      Essbase Writer Load Summary:
        Number of rows successfully processed: 0
        Number of rows rejected: 0

      at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
      at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
      at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2457)
      at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
      at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
      at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
      at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
      at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
      at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
      at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1595)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
      at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070)
      at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
      at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:49)
      at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
      at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
      at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
      at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
      at oracle.odi.runtime.agent.RuntimeAgent.startScenario(RuntimeAgent.java:777)
      at oracle.odi.runtime.agent.InternalRuntimeAgent.startScenario(InternalRuntimeAgent.java:52)
      at com.sunopsis.dwg.tools.StartScen.startScenOnLocalAgent(StartScen.java:994)
      at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java:242)
      at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:162)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3430)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeOdiCommand(SnpSessTaskSql.java:1491)
      at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:32)
      at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:1)
      at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
      at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
      at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
      at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
      at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1595)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
      at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
      at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070)
      at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
      at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:49)
      at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
      at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
      at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
      at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
      at oracle.odi.runtime.agent.RuntimeAgent.startScenario(RuntimeAgent.java:402)
      at oracle.odi.StartScen.run(StartScen.java:202)
      at oracle.odi.StartScen.main(StartScen.java:317)

       

      Best Regards

      Lasya Narasimham

        • 1. Re: ODI Warning
          mRainey

          Hi Lasya,

           

          What are the Options and Option values for the IKM in your Interface?

           

          Regards,

          Michael Rainey

          • 2. Re: ODI Warning
            Las071214

            Hi mRainey,

             

            Thank you for the response.Below are the options set for KM

             

            Name Value
            GROUP_ID<default>:1
            BUFFER_ID<default>:1
            BUFFER_SIZE<default>:80
            CLEAR_DATABASE<default>:None
            MAXIMUM_ERRORS_ALLOWED<default>:1
            COMMIT_INTERVAL<default>:1000

             

            But I have changed one of the options as below and checked in operator assuming I may get additional information on the warning but could not find any

            MAXIMUM_ERRORS_ALLOWED0

             

            Thanks & Regards

            Lasya Narasimham

            • 3. Re: ODI Warning
              mRainey

              Hi Lasya,

               

              I see that you're using a custom IKM rather than the OOTB delivered IKM SQL to Hyperion Essbase (DATA). In this IKM, there are Options for the log and error file directory and name. Can you check the data load step in your KM to see if there is a hardcoded location for the .log and .err files? This is where you'll be able to find further information about the progress and failure that occurred.

               

              Regards,

              Michael Rainey

              • 4. Re: ODI Warning
                Las071214

                Hi Rainey,

                 

                Thankyou for the valuable information. I have checked the log and error files. Error file is empty. I assume, since it is a warning, nothing is routed to error file.

                Below is the log infrmation. I couldnot predict any thing unsual in the log except for the word DEBUG at last 3rd line. Please suggest.

                 

                Log File Information :

                 

                2016-03-18 07:22:12,489 INFO  [SimpleAsyncTaskExecutor-2]: ODI Hyperion Essbase Adapter Version 9.3.1.1

                2016-03-18 07:22:12,489 INFO  [SimpleAsyncTaskExecutor-2]: Connecting to Essbase application [AppName] on [ServerName]:[1423] using username [odilogin].

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Successfully connected to the Essbase application.

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option PRE_LOAD_MAXL_SCRIPT =

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option POST_LOAD_MAXL_SCRIPT =

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option ABORT_ON_PRE_MAXL_ERROR = true

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option CLEAR_DATABASE = None

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option COMMIT_INTERVAL = 1000

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option BUFFER_ID = 1

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option BUFFER_SIZE = 80

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option GROUP_ID = 1

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option CALCULATION_SCRIPT = ExecuteAll

                2016-03-18 07:22:12,520 INFO  [SimpleAsyncTaskExecutor-2]: Essbase Load IKM option RUN_CALC_SCRIPT_ONLY = true

                2016-03-18 07:22:12,552 DEBUG [SimpleAsyncTaskExecutor-2]: LoadData Begins

                2016-03-18 07:22:12,552 INFO  [SimpleAsyncTaskExecutor-2]: Executing calculation script

                2016-03-18 07:24:07,430 INFO  [SimpleAsyncTaskExecutor-2]: Logging out and disconnecting from the essbase application.

                 

                Thanks & Regards

                Lasya Narasimham

                • 5. Re: ODI Warning
                  JohnGoodwin

                  Sorry what are you trying to fix, the warning you are getting is normal and the way the KM works, it is indicating no data has been loaded to Essbase so you would need to check the code that has been generated for  each step in the operator and can manually run the SQL that has been generated to see why no records are being loaded.

                  If you are want to change the way the warning works have a look at something I wrote back in the days of ODI 10 which is still relevant for 11 - More to life...: ODI – Hyperion Knowledge Modules - Reporting statistics correctly

                   

                  Cheers

                   

                  John

                  1 person found this helpful
                  • 6. Re: ODI Warning
                    Las071214

                    Hi John,

                     

                    Thank you for the suggestion. The filter is set in a way that no records are loaded to the target.

                    I went through your blog. I updated the report statistics in KM. I unchecked "Ignore Errors" and tried running it. It failed with below error.Kindly suggest.

                     

                    org.apache.bsf.BSFException: exception from Jython:
                    Traceback (most recent call last):
                      File "<string>", line 2, in <module>
                    Essbase Writer Load Summary:
                      Number of rows successfully processed: 0
                      Number of rows rejected: 0

                    at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
                    at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
                    at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
                    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2457)
                    at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
                    at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
                    at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
                    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
                    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
                    at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
                    at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
                    at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
                    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
                    at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
                    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
                    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
                    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
                    at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
                    at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
                    at java.lang.Thread.run(Thread.java:619)

                     

                    Thanks & Regards

                    Lasya Narasimham

                    • 7. Re: ODI Warning
                      JohnGoodwin

                      It is still generating the same error as before so it doesn't look like you have implemented the changes in the KM correctly or maybe you are running a scenario and it needs regenerating 

                      • 8. Re: ODI Warning
                        Las071214


                        Hi John,

                         

                        I just rechecked. I am running the updated package.

                        The error message is same but earlier it was a warning and pacakge was successful. After updating Report statistics , the package failed at Report statistics with the Error.

                         

                        I have only updated the Report statics in KM by unchecking the Ignore Error. I have not made any changes to the script (Command on Target).Please let me know if I have to do anyother changes.

                         

                        Thanks & Regards

                        Lasya Narasimham

                        • 9. Re: ODI Warning
                          JohnGoodwin

                          If you have only deselected "ignore errors" then it will fail because the step is raising an exception, in my example it is like that because the code has been changed so an exception has not been raised which mean it is ok to not have "ignore errors" selected.

                          If you are not changing the code then you will need to have "ignore errors" selected.

                          1 person found this helpful
                          • 10. Re: ODI Warning
                            Las071214

                            Hi John

                             

                            I have updated the code in Report Statistics in KM and able to fix the warning.Thank you very much for all the help

                             

                            Regards

                            Lasya Narasimham