Categories
- All Categories
- 145 Oracle Analytics News
- 27 Oracle Analytics Videos
- 14.7K Oracle Analytics Forums
- 5.7K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 54 Oracle Analytics Trainings
- 12 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
OBIA 11.1.1.10.2 - Load Plan 'Domain-only Extract and Load (SDE and SIL)' fails at Generate Failed T

<?xml version="1.0" encoding="ISO-8859-1"?>
<SunopsisExport>
<Admin RepositoryVersion="04.03.04.02" />
<Object class="com.sunopsis.dwg.dbobj.SnpSession">
<Field name="AgentName" type="java.lang.String"><![CDATA[OracleDIAgent]]></Field>
<Field name="ContextCode" type="java.lang.String"><![CDATA[GLOBAL]]></Field>
<Field name="ErrorMessage" type="java.lang.String"><![CDATA[ODI-1217: Session GENERATE_SUMMARY_REPORT (2094500) fails with return code 7000.
ODI-1226: Step Generate Failed Tasks Report fails after 1 attempt(s).
ODI-1232: Procedure Generate Failed Tasks Report execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 76, in <module>
>>>>>>Raising Custom Exception>>>>>> Error generating report file: /u01/app/obitest/product/fmw11g/instances/instance1/biapps/logs/etl/BIA_DW_ETL_LPI_Summary_10500_1_2094500.html
java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier
at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146) | |
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322) | |
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170) | |
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2474) | |
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48) | |
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:2925) | |
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2637) | |
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:2093) | |
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1899) | |
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:583) | |
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216) | |
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:514) | |
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1074) | |
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:133) | |
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:85) | |
at java.lang.Thread.run(Thread.java:662) |
Caused by: Traceback (most recent call last):
File "<string>", line 76, in <module>
We are using linux. Please help to solve the issue. Thanks,
Answers
-
Hi,
Are you able to access the path /u01/app/obitest/product/fmw11g/instances/instance1/biapps/logs/etl/ ?
If possible share us the screenshot of the error to debug more.
Thanks,
Yaswanth
0 -
Hi Venkata,
Thanks for response. Yes we can access the this path and there is no error while accessing.
Thanks,
0 -
Hi,
Can you share us the screenshot of the error in the load plan.
Thanks,
Yaswanth
0 -
0
-
Hi,
Share the session report any time when anyone ask for screenshot to be a best practice because it will be the lowest level the granularity which helps to debug the issue easily instead of multiple cross questions. Can you share the session log like below so that we can trace easily at which step the load failed.
Thanks,
Yaswanth
0