Oracle Realtime Scheduling (ORS) v1 Database Updates Stuck In 'Initiated' Due to GUI or Process Running With a Different or Invalid Timezone

(Doc ID 1097777.1)

Last updated on APRIL 16, 2015

Applies to:

Oracle Real-Time Scheduler - Version: 10.3 and later   [Release: 10.3 and later ]
Information in this document applies to any platform.


Some updates to ORS are not processing.

e.g. SELECT * FROM resource_manager.stop a WHERE a.stop_id = '107054132/T1'

The update is stuck in ‘initiated’, however reports success in web service.

This example is from 8am, but by 4pm the customer had 30 outstanding database updates stuck in INITIATED which caused quite a problem for schedulers allocating work to techs throughout the day since the current status was not known. Manual intervention was required to reprocess. These stuck statuses happened throughout the day.


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