Scheduler Manager Batch Job Crashed with Caught Signal 11 Segmentation Fault and Duplicate Key Error
(Doc ID 2405372.1)
Last updated on SEPTEMBER 23, 2022
Applies to:
Oracle Real-Time Scheduler - Version 2.3.0.0.0 and laterOracle Utilities Mobile Workforce Management - Version 2.3.0.0.0 and later
Oracle Mobile Workforce Cloud Service - Version NA and later
Information in this document applies to any platform.
Symptoms
MWM - Oracle Utilities Mobile Workforce Management
CM-SM batch job has crashed with the following error on Batch Run:
ERROR
-----------------------
Informational - SchedBatchProcessWorker - Batch thread 1 of 1 started at 201x-01-22-22.45.48
Informational - SchedBatchProcess$SchedBatchProcessWorker - Scheduler GSWCALL started at 01-22-201x 10:45PM
Error - SchedulerErrorRunnable$CreateErrorMessage - Scheduler error [Caught signal 11 Segmentation fault] at 201x-01-22-14.28.47
Error - SchedulerErrorRunnable$CreateErrorMessage - Scheduler error [Attempting to flush all open files] at 201x-01-22-14.28.47
Severe - SchedBatchProcessWorker - Duplicate key error: 1714507 4
Informational - SchedBatchProcessWorker - Batch thread 1 ended abnormally at time 2018-02-20-14.33.51
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |