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 NOVEMBER 03, 2015

Applies to:

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


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

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.


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