Scheduled ODI scenario auto executed twice!!

Hi All,
I am using ODI 10.1.3.5 . I have an ODI scenario scheduled to run once everyday midnight. Normally it runs fine but on some irregular intervals, the scenario simply doesn't run or runs twice at the scheduled time . Does anyone has any idea how to investigate/ solve this issue. Please help.
I have checked in the SNP_PLAN_AGENT table and the entry is there as it should be .
Thanks,
Saby

Not running a scheduled job sounds like a bug. please work with support channel to further investigation.
You can check with view schedule dialog for a agent and see if its showing the scheduled jobs correctly. If so then agent should execute them on scheduled time.
On running it twice: please check if you have configured the job to retry on failure or run multiple times. Otherwise this too sounds like a bug to me.

Similar Messages

Schedule a scenario to execute as soon as it gets completed

Hi,
Is it possible to schedule a scenario to execute again as soon as it gets completed?
Please let me know.
Thanks!

Hi,
If you want you scenario to go in an endless loop, you can simply create a new package. Drag your scenario into the new package, and add the "OK" to itself. Therefore unless it fails it will start again on completion.
You may want to add a variable to you package so you can stop it, which you can set externally.
The Final package would look like this...
Declare variable-->Refresh variable-->evaluate variable (true)-->call scenario loop back to Refresh variable (step 2).
If the evaluate variable is false, then the package will stop.
Cheers
Bos

Scheduling A Scenario Through ODI Console

Hi,
I want to schedule a ODI Scenario through ODI Console.Is it possible?If yes, then please let me know how??Because I am able only to execute the odi scenario through odi console.But can't scheduled it(Can't find any option there)
Thanks
Anindya

Nope
http://docs.oracle.com/cd/E28271_01/integrate.1111/e12643/running_executions.htm#BABBEDEG
you can schedule it using sdk.
http://dwteam.in/scheduling-in-odi-using-sdk/

How to execute ODI scenario from a web application

Hi
I need to execute ODI scenario from ApEx form.
how to execute ODI scenario from application. Using 10.1.3.5.5
-app

In the SQL property of the TQuery object, enter the call as an anonymous block:
begin
pkg_name.procedure_name(true);
end;

Problem in Creating and Scheduling an ODI Scenario

Hi,
while Creating and Scheduling an ODI Scenario with the help of the following link:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/10g/10135/creating_scheduling_scenario/creating_scheduling_scenario.htm#t2
Oracle DI Agent is not listed in services window(Start>Control Panel>Administrative Tools > Services).
What shall I do?
please tell me.And in addition please tell me the use of the Oracle DI Agent and why should we stop its service before creating the schedule??
Thanks
Anindya

Please also look into this link http://odiexperts.com/agent/
First of all did you got any Error why creating Agent Server else the agent service should be visible.
Else please try this step.
Update Odiparams
agentservice -i -s <agent_name>
Go and look for Services starting with Oracledi_Agent_<agentNAME> and start it Finally test the agent and you should be able to schedule.
you dont need to stop the Agent for every new Schedule, but you will need to right click on Agent and click on Update Scheduling -http://odiexperts.com/scheduling-using-odi-scheduler/
If you are getting an error please provide us the error info and step at which you got the error.

When I schedule a Job, the job is executed twice.

Post Author: sachinddalal
CA Forum: Data Integration
Hello,
I am using Data Integrator Ver 11.0.2.22. I have scheduled the job through Admin Console. When the job is executed it seems that the job is executed twice.
On the Status tab onDI Administrator, it shows that both the jobs started at same time. The end time of bot the job is different.
Any one have any idea how this happens?
Also any way to ensure that the job are not executed twice.
Thanks,
Regards
Sachin Dalal

Post Author: bhofmans
CA Forum: Data Integration
If you get this issue for a scheduled job only, I might be that the schedule is created twice in the OS scheduler. You could check the windows task scheduler (or cron on UNIX) to check for duplicate schedules.
If you see this issue also for jobs you execute manually (via webadmin or Designer), you can have this kind of problems if the same jobserver is registered multiple times in a repository. You can check the AL_MACHINE_INFO in your repository. It should have one line for each jobserver and one line for each administrator the repo is connected too. I suspect you have some duplicates there (you can just remove them - this table gets populated when adding a repo in the web admin and when adding a repo to a jobserver in the server manager).

Call an ODI scenario

Hello all,
Through a concurrent ORACLE can call an ODI scenario?
I think the only possibility to call an odi scenario is:
1 - Calling an ODI scenario through a command operating system (OS COMMAND)
2 - Calling an ODI scenario through a WebService - way more common today
3 - Calling an ODI scenario through a JAVA program.
these are the only options?

Create a bat file to run odiscenario and execute that bat file in oracle using job scheduler. Here is one example.
BEGIN
sys.dbms_scheduler.create_job(
job_name => 'testjob',
job_type => 'EXECUTABLE',
job_action => 'C:\WINDOWS\system32\cmd.exe',
repeat_interval => 'FREQ=WEEKLY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=5;BYMINUTE=0;BYSECOND=0',
start_date => systimestamp at time zone 'US/Eastern',
job_class => 'DEFAULT_JOB_CLASS',
comments => 'test job',
auto_drop => FALSE,
number_of_arguments => 3,
enabled => FALSE);
sys.dbms_scheduler.set_job_argument_value( job_name => 'testjob', argument_position => 1, argument_value => '/q');
sys.dbms_scheduler.set_job_argument_value( job_name => 'testjob', argument_position => 2, argument_value => '/c');
sys.dbms_scheduler.set_job_argument_value( job_name => 'testjob', argument_position => 3, argument_value => '"test.bat"');
sys.dbms_scheduler.enable( 'testjob' );
END;

Launch ODI scenario from PL/SQL

I want to execute ODI scenario from PL/SQL procedure.
1. I have created the java method using oracle.odi.sdk.invocation.*
// Create the scenario command
OdiCommandScenario cmd = new OdiCommandScenario();
cmd.setScenName(pckName);
cmd.setScenVersion(pckVer);
cmd.setSyncMode(lSyncMode);
cmd.setLogLevel(lLogLevel);
cmd.setContext(lCtx);
cmd.setSessionName(sesName);
// Additional variables
if (parNames != null) {
for (int j=0; j<parNames.length;j++) {
cmd.addVariable(parNames [j], parValues[j]);
// Create the repository connection
OdiRepositoryConnection conn = new OdiRepositoryConnection();
conn.setOdiUser(lOdiUsr);
conn.setOdiPassword(lOdiPwd);
// Launch scenario (use Agent scheduler)
try
invocation = new OdiInvocation(lHostName,lPortNum);
catch (Exception e2) { throw new Exception ("open OdiInvocation="+e2.getMessage());}
OdiInvocationResult result = invocation.invokeCommand(cmd,conn);
if (!result.isOk())
{throw new Exception ("invokeCommand="+result.getErrorMessage());}
else
{sid = result.getSessionNumber();}
invocation.close();
rv = "OK"+sid;
catch (Exception e) { rv = "ERROR: "+e.getMessage(); }
finally
return rv;
// System.exit(0); // !!
2. I have created a PL/SQL wrapper for this java method
It is working satisfactory, an ODI scenario is launched, ID of ODI session is returned, but a java session is not finished, it stay to hang up.
I have got the same result if I try to execute java-method directly from command line - session is hang up.
I found only workaroud to use "System.exit(0)" to terminate session, but it is not a way I can use inside JVM.
(I can to resolve it by deploying java method as web-service and call this webservice from DB - it works OK ... but it seems uselessly complicated ... )
Version ODI: 10.1.3.5.3, JDK 5.0, Windows (but I've got the same result on the Linux)
Any suggestions? Thank you very much.

In your example you invoke ODI scenario using "startscen" command (using java method for launching OS command from PL/SQL).
Yes, I have also tried this workaround - but it is complicated to get back a session ID or ODI error message. In addition to I had a problem with calling ODI scen asynchrounously - but I didn´t investigate this possibility too properly ...
Thanks

ERROR WHILE RUNNING ODI SCENARIO FROM BAM ALERT

We are using oracle data integrator 11g and have created an ODI Scenario and able to run the scenario from ODI studio client.
We have done the configuration for BAM-ODI integration as mentioned in http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/bam_odi.htm#BABEJIGD
We have started ODI Agent, soa and bam servers. Created a BAM alert -> select action - Run ODI Scenario -> selected the same scenario.
Alert ran at scheduled time but failed with following error:
java.io.IOException : truncated data integrator frame received
Error Message (if any)
[2012-08-06T11:24:21.046+05:30] [bam_server1] [WARNING] []
[oracle.bam.eventengine] [tid: bam-pool-Action-thread-1] [userId:
OracleSystemUser] [ecid:
3576f9092ef9497a:-743c430a:138fa7450c3:-8000-00000000000000a8,1:23453] [APP:
oracle-bam#11.1.1] EventEngine: Error occured while running a ODI Scenario.
[2012-08-06T11:24:21.250+05:30] [bam_server1] [ERROR] []
[oracle.bam.eventengine] [tid: bam-pool-Action-thread-1] [userId:
OracleSystemUser] [ecid:
3576f9092ef9497a:-743c430a:138fa7450c3:-8000-00000000000000a8,1:23453] [APP:
oracle-bam#11.1.1] EventEngine: Action exception: EEInstEv2 EEInstAct1 Rule
Id: 2 exception: java.io.IOException: truncated Data Integrator Frame
received
[2012-08-06T11:24:21.250+05:30] [bam_server1] [WARNING] []
[oracle.bam.eventengine] [tid: bam-pool-Action-thread-1] [userId:
OracleSystemUser] [ecid:
3576f9092ef9497a:-743c430a:138fa7450c3:-8000-00000000000000a8,1:23453] [APP:
oracle-bam#11.1.1] EventEngine: Exception stack trace: [[
at
oracle.bam.eventengine.engine.event.action.RunScenario.invokeScenario(RunScena
rio.java:145)
at
oracle.bam.eventengine.engine.event.action.ActionProcessor.runScenario(ActionP
rocessor.java:891)
at
oracle.bam.eventengine.engine.event.action.ActionProcessor.actionHandler(Actio
nProcessor.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j
ava:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.bam.system.Delegate$Sink.invoke(Delegate.java:80)
at oracle.bam.system.Delegate.dynamicInvoke(Delegate.java:186)
at
oracle.bam.common.threading.threadpool.ThreadPoolController$PoolQueueItem.proc
essWorkRequest(ThreadPoolController.java:155)
at
oracle.bam.common.threading.threadpool.ThreadPoolController$PoolQueueItem.run(
ThreadPoolController.java:128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java
:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908
at java.lang.Thread.run(Thread.java:619)
Any help on this is highly appreciated...
Thanks
Rajdip Mukherjee

Hi,
Forgot to include the ODI classes RunScenario.invokeScenario() is invoking odi scenario using odi sdk api. Please see the below stack trace :-
java.io.IOException: truncated Data Integrator Frame received
at
oracle.odi.sdk.invocation.internal.AgentNetworkCmd.readCmd(AgentNetworkCmd.java:303)
at
oracle.odi.sdk.invocation.OdiInvocation.invokeCommand(OdiInvocation.java:176)
at
oracle.bam.eventengine.engine.event.action.RunScenario.invokeScenario(RunScenario.java:140)
at
oracle.bam.eventengine.engine.event.action.ActionProcessor.runScenario(ActionProcessor.java:891)
at
oracle.bam.eventengine.engine.event.action.ActionProcessor.actionHandler(ActionProcessor.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Thanks
Rajdip Mukherjee

How to schedule the background job daily twice?

Hi,
How to schedule the background job daily twice? any conditions?
Regards,
Srihitha

see the step by step procedure.
Scheduling Background Jobs:
1. Background jobs are scheduled by Basis administrators using transaction SM36.
2. To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3. While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a. Time of printing: set to Send to SAP spooler Only for now
b. Name abbreviated name to identify the job output
c. Title free form description for the report output
d. Authorization a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e. Department set to appropriate department/functional area name. This field can be used in
a search later.
f. Retention period set to Do not delete if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1. To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2. To access a particular jobs output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3. Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1. Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks Parameters button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
Scheduling background jobs section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of Scheduling background jobs section).
Access to reports output:
1. A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2. The selection screen can be configured by clicking Further selection
criteria button (e.g. to bring Spool request name (suffix 2) field or hide other
fields).
3. The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobs outputs)
a. Spool request name (suffix 2) corresponds to a spool name in p. 3.b in
Scheduling background jobs section above).
b. Date created to find an output of a job that ran within a certain date range.
c. Title corresponds to spool Title in p. 3.c in Scheduling background jobs
section above).
d. Department - corresponds to spool Department in p. 3.e in Scheduling
background jobs section above).
4. Upon entering selection criteria, the user clicks the Execute button to
retrieve the list of matching spool requests.
5. From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a. Click the Print button to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b. Click the Print with changed attributed button to print the spool request
with the different attributes (e.g. changing the printer name).
c. Click the Display contents button to preview the spool request contents. A
Print and Download functions are available from the preview mode.

Error while running the ODI Scenario

Hi All,
I am trying to execute ODI Scenario from operator window getting below error. I am not sure why the error is comming yesterday it was running successfully.
I checked the agent connection via test button, it is working fine.
com.sunopsis.dwg.cmd.b: Error during Scenario launching : Error during Session Preparation : You are trying to execute a session with an agent that is undefined in your repository. Please check the agent -NAME parameter.
     at com.sunopsis.dwg.dbobj.SnpScen.a(SnpScen.java)
     at com.sunopsis.dwg.dbobj.SnpScen.remoteExecute(SnpScen.java)
     at com.sunopsis.dwg.dbobj.SnpScen.remoteExecute(SnpScen.java)
     at com.sunopsis.graphical.g.ot.m(ot.java)
     at com.sunopsis.graphical.o.z.actionPerformed(z.java)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
     at com.jidesoft.plaf.vsnet.VsnetMenuItemUI.doClick(Unknown Source)
     at com.jidesoft.plaf.vsnet.VsnetMenuItemUI$MouseInputHandler.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Component.java:6263)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
     at java.awt.Component.processEvent(Component.java:6028)
     at java.awt.Container.processEvent(Container.java:2041)
     at java.awt.Component.dispatchEventImpl(Component.java:4630)
     at java.awt.Container.dispatchEventImpl(Container.java:2099)
     at java.awt.Component.dispatchEvent(Component.java:4460)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
     at java.awt.Container.dispatchEventImpl(Container.java:2085)
     at java.awt.Window.dispatchEventImpl(Window.java:2478)
     at java.awt.Component.dispatchEvent(Component.java:4460)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

I'm guessing the name on the physical agent was different from the agent name of the process running on the server? That's generally when I get this error...

Invoking ODI Scenario from a BPEL process - Resolved

I new to Oracle products.
I am exploring Oracle Data Integrator tool.
I would like to call ODI scenario from a BPEL process.
I created a scenario in ODI, I have SOA suite10.1.3.3 installed in my machine.
In some portal I have read that, we need to deploy apache axis to Oracle App server and then deploy the ODI public web service to axis. This public web service facilitates us to call scenario from partner link.
Following are my questions:
1) I guess Oracle App server acts as webservice container too. Why should I use apache axis here?
2)If axis must be used, please let me know how to deploy it to OAS.
If axis is not required, please guide me how to deploy public web service to OAS.
Thanks!!

Hi:
I have similar problem, when invoke ODI Scenario from a BPEL Process, the error in ODI Designer is:
java.lang.NullPointerException
     at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.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.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Thread.java:595)
In the BPEL Console the result is OK and process complete, but in the INVOKE scenario send message:
<messages><ODI_REQUEST><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><invokeScenarioRequest xmlns="xmlns.oracle.com/odi/OdiInvoke/">
*<RepositoryConnection xmlns=""*
<JdbcDriver>oracle.jdbc.driver.OracleDriver</JdbcDriver>
<JdbcUrl>jdbc:oracle:thin:@192.168.1.109:1521:ORCL</JdbcUrl>
<JdbcUser>dimaster</JdbcUser>
<JdbcPassword>sabr0sa</JdbcPassword>
<OdiUser>SUPERVISOR</OdiUser>
<OdiPassword>SUNOPSIS</OdiPassword>
<WorkRepository>TESTWORKREP1</WorkRepository>
</RepositoryConnection>
*<Command xmlns="">*
<ScenName>P_TRASPASOSOP09</ScenName>
<ScenVersion>2</ScenVersion>
<Context>Global</Context>
<LogLevel>5</LogLevel>
<SyncMode>0</SyncMode>
<SessionName/>
<Keywords/>
<Variables>
<Name/>
<Value xmlns:ns1="http://xmlns.oracle.com/Recepcion">
<ns1:Escenario>P_TRASPASOSOP09</ns1:Escenario>
<ns1:Version>2</ns1:Version>
<ns1:Contexto>Global</ns1:Contexto>
<ns1:ID>1</ns1:ID>
<ns1:NivelLogeo>5</ns1:NivelLogeo>
</Value>
</Variables>
</Command>
*<Agent xmlns="">*
<Host>192.168.1.109</Host>
<Port>20910</Port>
</Agent>
</invokeScenarioRequest>
</part></ODI_REQUEST><ODI_RESPONSE><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><odi:invokeScenarioResponse xmlns:odi="xmlns.oracle.com/odi/OdiInvoke/">
<odi:CommandResultType>
<odi:Ok>true</odi:Ok>
<odi:SessionNumber>445000</odi:SessionNumber>
</odi:CommandResultType>
</odi:invokeScenarioResponse>
</part></ODI_RESPONSE></messages>

Invoking ODI scenario from BPEL using Asynchronous callbacks

It has been given in many sites that for invoking an odi scenario, odi-public-ws.aar must be uploaded to AXIS2 framework as the web service uses AXIS2 as the web service container. For doing this first the AXIS2 should be deployed in OC4J.
I am working with a scenario like this. I didnt deploy AXIS2 and neither uploaded the odi-public-ws.aar. Still i am getting the result as success. BPEL is invoking the ODI scenario and callback is happening too.
I, also tried invoking ODI scenario in a remote system. Got the result for that too. I am using ODI 10.1.3.4 and J-Dev 10.1.3.3 and SOA suite 10.1.3.1.
Can anyone suggest how without AXIS2 framework the process is success?

Hi,
Thanks its working now. I am facing another issue. I do not use parameters in my Scenario. Now when i run my scenario i m getting the following error. I think its because i have not assigned anything to the Variable element. I guess its taking null value for Variable element here and cheking if such a variable exists. Have you come accross such an issue? If so, please sugest remedy.
java.lang.Exception: Specified variable not found in the Repository : null
     at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.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.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Thread.java:619)
Edited by: silas.john on May 13, 2009 1:29 AM

Problems with the call of an ODI scenario from an OS Command.

I'm having a trouble to understanding regarding the call an ODI scenario from an OS Command.
On the machine "XPTO" is installed the Agent.
For my local computer, by Designer ODI I can usually run the scenarios, using the Agent that is installed in the machine "XPTO".
When attempting to run ODI scenario directly from the machine "XPTO", where we have the agent installed within the /Ora_Home/oracledi/bin the file STARTSCEN.BAT not exist.
On the machine where you installed the agent I should also have the client installed, so as to be able to run the StartScen.bat?

As suggested, I ran the following command line:
*./startcmd.sh OdiStartScen -SCEN_NAME=STG_CRTC -SCEN_VERSION=001 -CONTEXT=GLOBAL -AGENT_CODE=ODI_2001*
But gave the error below:
com.sunopsis.core.f:*
at com.sunopsis.tools.connection.DwgRepositoryConnectionsCreator.a(DwgRepositoryConnectionsCreator.java)*
at com.sunopsis.tools.connection.DwgRepositoryConnectionsCreator.a(DwgRepositoryConnectionsCreator.java)*
at com.sunopsis.tools.connection.DwgRepositoryConnectionsCreator.a(DwgRepositoryConnectionsCreator.java)*
at com.sunopsis.tools.connection.DwgRepositoryConnectionsCreator.a(DwgRepositoryConnectionsCreator.java)*
at com.sunopsis.security.c.b(c.java)*
at com.sunopsis.security.c.b(c.java)*
at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.u(SnpsFunctionBaseRepositoryConnected.java)*
at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java)*
at com.sunopsis.dwg.tools.StartScen.main(StartScen.java)*
at com.sunopsis.dwg.tools.OdiStartScen.main(OdiStartScen.java)*
Can anyone help me?

ODI Scenario Hang on ODI Procedure

Hi Experts,
We have one ODI scenario which consists of a few ODI procedure steps with anonymous PL/SQL block. When one procedure takes a long time to process data (>60min. when data volume is large), the ODI scenario hangs intermittently on the procedure (ODI Operator shows Running state and no progress to next step in Scenario). The pl/sql script finished fine when running against database directly processing the same dataset.
When the ODI step hangs, the database side where the pl/sql runs on has no more activities, and the db session(v$session) which processes the ODI procedure goes away as well (db session not existing on db anymore). But the ODI Operator still shows the step in running state and hangs there forever (days). The jdbc connection from ODI to db looks fine.
How can we fix this problem in ODI? The ODI version is 10.1.3.5.
Appreciate your input on this.
Thanks,

The doc said "If your command is being executed in a transaction (numbered 0 to 9)" then I should set 'Commit'. But I used 'Autocommit' for transaction, is the 'Commit' necessary here?
Thanks!

Scheduled ODI scenario auto executed twice!!

Similar Messages

Maybe you are looking for