Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

What is the possilble reason when odi failed to launch a scenario?

671265Aug 6 2010 — edited Aug 15 2010
I have a scenario containing 3 child-scenario. Two of them are settled on agent1, which are running in Asynchronous Mode, and the third one is settled on agent2, which is running after the other two in Synchronous Mode. The father-scenario is scheduled to run every hour. Before and after 'Aug 7, 2010 12:12:51 AM', the fater-scenario runs well. But it suddently failed at 'Aug 7, 2010 12:12:51 AM' with return code 7000 and detail message as below,
com.sunopsis.dwg.cmd.c: Error during Scenario launching
	at com.sunopsis.dwg.dbobj.SnpScen.a(SnpScen.java)
	at com.sunopsis.dwg.dbobj.SnpScen.remoteExecuteSynchrone(SnpScen.java)
	at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java)
	at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java)
	at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java)
	at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
	at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(SnpSessTaskSqlS.java)
	at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
	at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
	at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
	at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
	at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
	at com.sunopsis.dwg.cmd.e.i(e.java)
	at com.sunopsis.dwg.cmd.g.y(g.java)
	at com.sunopsis.dwg.cmd.e.run(e.java)
	at java.lang.Thread.run(Thread.java:595)
It seems like a agent problem. I got a monitor/start odi agent scripts runs every minute on server, the scripts is as below,
#!/bin/bash
# It used to run odi agent while it down.
# wangdj 2010-7-26

odi_agent_count=`ps -ef|grep pinglog_agent|grep odi|grep -v grep|wc -l`
if [ $odi_agent_count -ne 2 ]; then
   if [ $odi_agent_count -ne 1 ]; then
      . ~oracle/.odiprofile
      #ODI_HOME=/U01/app/oracle/product/odi/oracledi/
      #cd $ODI_HOME/bin/
      nohup $ODI_HOME/bin/agent.sh -PORT=29010 -NAME=pinglog_agent >> /tmp/odi_agent.log &
   fi
fi
From the log, there was no operation of re-starting agent. It means the agent wasn't down at that time.

This event makes me very confused. I don't how to find any reasons related to it. Anyone could give me a hint?

Any comments will be appreaciated!!!


Best wishes,
Satine
This post has been answered by Cezar Santos on Aug 13 2010
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 12 2010
Added on Aug 6 2010
6 comments
2,752 views