Receiving "No Such Shift" Error in ORS And All Orders Remain Unassigned After a Network Outage
(Doc ID 1264829.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Real-Time Scheduler - Version 22.214.171.124.0 to 4.5.0 [Release 4.2 to 4.5]
Information in this document applies to any platform.
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.
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)
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
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