Last updated on SEPTEMBER 30, 2010
Applies to:Oracle Enterprise Real Time Scheduling - Version: 1.13.0
Information in this document applies to any platform.
In this example a job was started on a shift at 10:49am.
The system date was advanced to 23:57. At this point RMGW archived all shifts including the started shift 12037-20100721-0.
The single stop on this shift with a status of 'STARTED' was therefore disabled and moved to the free bar in the Planner GUI. This reproduces a real world scenario where the mobile device has failed and has therefore been unable to progress the status of the job to COMPLETE. In the real world scenario, at some point the mobile device would become active again (e.g. once battery has been recharged). When this happens, the STOP_COMPLETED message is sent to the web service. The web service correctly processes this message and the Resource Manager Gateway in turn correctly processes the message.
RMGW480 22/07/10 00:08:18.29 Stop <103-e> and all stops from job <103-e> are not longer active, will be archived
RMGW480 22/07/10 00:08:18.37 Inserting stop <103-e> into archive
The stop is correctly removed from the stop table and placed in the stop_archive table. However the gateway fails to send a 'STOP_DEL' message to the switch and therefore the stop remains visible within the ORS Client. The only way to remove the stop from the client is to manually delete it or to restart the gateway
### Impact on Business ###
ORS wrongly indicates that there is a stop in the schedule that needs attention.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms