java.lang.RuntimeException

Error occured in open tool execute method: {0}...Error in executing ABAP program: {0}...File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web42741

  • via Oracle Community by 2875303, 10 months ago
    Error occured in open tool execute method: {0}...Error in executing ABAP program: {0}...File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open.
  • Error occured in open tool execute method: {0}...Error in executing ABAP program: {0}...Syntax error in program SAPLZODI_FGR_6501 . Cause: Syntax error in program SAPLZODI_FGR_6501 . Cause: Syntax error in program SAPLZODI_FGR_6501 .
  • via Oracle Community by Drona, 1 year ago
    Error occured in open tool execute method...Error in creating SAP Connection pool...User ORACLEBI has no RFC authorization for function group SYST. on <sap-hostname> sysnr 52 Cause: User ORACLEBI has no RFC authorization for function group SYST. on
  • Stack trace

    • java.lang.RuntimeException: Error occured in open tool execute method: {0}...Error in executing ABAP program: {0}...File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. Cause: File "/usr/sap/integracao_odi_sap/ZODI_8525001_3630001_DESENVOLVIMENTO.txt" is not open. at oracle.odi.sap.km._OdiSapAbapExecute.chainedSAPException(_OdiSapAbapExecute.java:746) at oracle.odi.sap.km._OdiSapAbapExecute.execute(_OdiSapAbapExecute.java:689) at com.sunopsis.dwg.function.SnpsOpenToolFunction.actionExecute(SnpsOpenToolFunction.java:47) at com.sunopsis.dwg.function.SnpsOpenToolFunction.execute(SnpsOpenToolFunction.java:148) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3437) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeOdiCommand(SnpSessTaskSql.java:1509) at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:44) 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:2913) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625) at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:580) at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468) at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366) at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855) at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126) at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.