Scheduler Submit Jobs Ending With Exit Code 0 Due To Connection Conflict From Multiple Batches
Last updated on SEPTEMBER 20, 2016
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.2.0 and later
Oracle Real-Time Scheduler - Version 2.2.0 and later
Information in this document applies to any platform.
When a scheduler batch is submitted, it is identified that the batch completes with exit code 0.
Since this is a scheduler batch, we expect this to be running until there is manual intervention to kill the process.
We have seen this issue across standalone and cluster interfaces.
The workaround which is being implemented is to resubmit the scheduler batch, when the batch is resubmitted, the batch does not complete.
Can you please advise if there are any configuration tuning required to mitigate this issue.
Batches are submitted from the command line as example:
$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON -c "$SPLEBASE/bin/submitjob_ORS.sh -b CM-MLO1 -p Sched_1"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms