MWM/ORS Scheduler Crashes With Unique Key Exception On IBM AIX (Doc ID 2576165.1)

Last updated on MAY 01, 2023

Applies to:

Symptoms

MWM/ORS Scheduler Crashes With Unique Key Exception on IBM AIX

ERROR
-----------------------
Exception Message: Causing the Scheduler to stop.

11:53:29,904 [SCHEDULERWorker:0] ERROR (com.splwg.mwm.domain.scheduler.batch.SchedBatchProcess) Scheduler ONE stopped at 2019-06-27-11.53.29
11:53:29,918 [SCHEDULERWorker:0] ERROR (com.splwg.mwm.domain.scheduler.batch.SchedBatchProcess) Failed to log error message to the batch run tree
11:53:30,024 [SCHEDULERWorker:0] ERROR (com.splwg.base.api.batch.AbstractExecutionStrategy) Thread execution aborted: BatchThreadInstance_Id(batchThreadId: [batchRunId: [batchControlId: [ID], batchNumber: 1, batchRerunNumber: 0], batchThreadNumber: 1], batchInstance: 12345678)
com.splwg.base.support.grid.GridWorkAbortedException: com.splwg.shared.common.ApplicationError: (Server Message)
Category: 11001
Number: 403
Call Sequence:
Program Name:
Text: Duplicate key error: 12,830,949 4
Description: Every record on a table must have a unique key. There's already a record whose key matches the value(s) you specified. If you want to save this information, you must either change the key to be something that doesn't already exist OR display the existing record and change it.
Table: null
Field: null
at com.splwg.base.support.batch.Java

SCH758 (MAIN) 27/06/19 11:53:09.108 [00:00:08.480] Starting Internal Event <
ImmediateAssignment_SH >.
SCH758 (MAIN) 27/06/19 11:53:09.167 [00:00:08.540] Caught signal 11
SCH758 (MAIN) 27/06/19 11:53:09.167 [00:00:08.540] Segmentation fault
SCH758 (MAIN) 27/06/19 11:53:09.167 [00:00:08.540] Attempting to flush all open files
Log file for <scheduler-2.3.0.3.36179-ibm>

Changes

Cause

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