My Oracle Support Banner

Batch Jobs Terminated With Exit Code 2 Due to Submitter Timed Out Due To Unsupported DISTRIBUTED Batch Mode (Doc ID 2073483.1)

Last updated on SEPTEMBER 19, 2022

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.1.0.6 and later
Oracle Real-Time Scheduler - Version 2.1.0.6 and later
Information in this document applies to any platform.

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:

MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
DBA - Database Administrator
RMAN - Recovery Manager
RAC - Oracle Real Application Clusters

Many batch jobs terminated with Exit Code 2, but these jobs were completed in MWM.

ERROR
-----------------------
An exception was thrown - terminating this run with exit code 2

Also, regular RMAN logs of the database had gone from 8 GB to 80 GB. There were no changes to the application or the database.
The DBA added disk space to get the RAC server back up and provide space for the RMAN backups to run.  The database is being monitored for expensive SQL statements, looping statements, long running processes and high table growth, but there is nothing unusual other than the F1_TSPACE_ENTRY table growing rapidly.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.