Scheduler Submit Jobs Ending With Exit Code 0 Due To Connection Conflict From Multiple Batches
(Doc ID 2184769.1)
Last updated on JANUARY 05, 2021
Applies to:Oracle Utilities Mobile Workforce Management - Version 18.104.22.168.0 and later
Oracle Real-Time Scheduler - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
TPW - Threadpoolworker
CPU - Central Processing Unit
IO - Input/Output
CM - Customer Modification
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"
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!