Recieving "No Such Shift" Error in ORS And All Orders Remain Unassigned After a Network Outage (Doc ID 1264829.1)

Last updated on NOVEMBER 09, 2010

Applies to:

Oracle Enterprise Real Time Scheduling - Version: 4.2 to 4.5.0 - Release: 4.2 to
Information in this document applies to any platform.

Symptoms

All orders are in an unassigned status and Oracle Realtime Scheduler (ORS) scheduler is not assigning orders to crews. When orders are manually dispatched to the crew through the Mobile Workforce Management (MWM) Dispatcher Workstation (DW) users get the one-line error "No Such Shift". Warnings appear in the MWM Server and ORS Smauto log.

MWM SvTraceX.log

WARN|2010-11-03 02:02:25|2956|No active shift record was found for Crew [XYZ]. (XThreadSvShift::ProcessNextShift) (::)
INFO|2010-11-03 02:02:25|3700|WARNING: No active shift record was found for Crew [XYZ]. (CServerDlg::WriteAuditMessage)
INFO|2010-11-03 02:02:25|2956|Future shift id [XYZ-20101103] has been activated. (XThreadSvShift::ProcessNextShift)

ORS smautoxxx.log

SCH700 03/11/10 09:01:17.77 recv SWITCH.1716 0014:202812 >>JOB_ALLOC_COND|000000000000167754|XYZ-20101103|1e+010<<
SCH700 03/11/10 09:01:17.79 send SWITCH.1716 0014:847272 >>ERROR|||JOB_ALLOC_COND||||||||No such shift <XYZ-20101103><<
SCH700 03/11/10 09:01:17.79 ERROR: (No such shift <XYZ-20101103>) generated in gen\src\request\requestUtil.c at line 190


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