Recieving "Failed to update stop_sched for Stop <XXX>: ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS) violated..." after MWM upgrade with ORS Integration (Doc ID 1146323.1)

Last updated on JULY 09, 2010

Applies to:

Oracle Enterprise Real Time Scheduling - Version: 10.3 to 1.13.0 - Release: 10.3 to
Oracle Utilities Mobile Workforce Management - Version: 1.5.0 to 1.5.0   [Release: 1.5 to 1.5]
Information in this document applies to any platform.

Symptoms


After an upgrade to Mobile Workforce Management (MWM) 1.5, users began to see system messages on the Dispatcher Workstation (DW) stating (ORS.CHK_STOP_SCHED_STATUS).  Sometimes the orders being referenced in this message have already been scheduled.  There are also errors in Oracle Realtime Scheduler (ORS) Resource Manager Gateway (RMGW) logs.  All of the data appears to be valid in the database and the Dispatcher Workstation.

What do these message mean? Is this an informational type error message or an error that will affect the operational scheduling of orders?

Dispatcher Workstation System Message Example

RTS:STOP Z5709371811XYZ: Failed to update stop_sched for Stop <D5709371811035>: ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS) violated QOCI: Unable to execute statement.


ORS Resource Manager Gateway Message Example

RMGW140 01/07/10 08:50:23.59 WARNING: assertion << Failed to update stop
sched: ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS)
violated^JQOCI: Unable to execute statement >> failed in
gen\src\rmGen\rmStops.c at line 1521: continuing
RMGW140 01/07/10 08:50:23.59 Failed to update stop_sched for Stop
<Z5709371811XYZ>: ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS)
violated^JQOCI: Unable to execute statement
RMGW140 01/07/10 08:50:23.59 Failed to update stop_sched for Stop
<Z5709371811XYZ>: ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS)
violated^JQOCI: Unable to execute statement
RMGW140 01/07/10 08:50:23.59 Error: STOP <Z5709371811XYZ> - Failed to update
stop_sched for Stop <Z5709371811XYZ>: ORA-02290: check constraint
(ORS.CHK_STOP_SCHED_STATUS) violated^JQOCI: Unable to execute statement
RMGW140 01/07/10 08:50:23.73 Inserted record <179909>
<STOP:Z5709371811XYZ:Failed to update stop_sched for Stop <Z5709371811XYZ>:
ORA-02290: check constraint (ORS.CHK_STOP_SCHED_STATUS) violated^JQOCI:
Unable to execute statement> into <alert> table

Changes

This issue may occur after an upgrade from MWM 1.4 to MWM 1.5.

Cause

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