My Oracle Support Banner

Cannot Connect to ORS Planner Client Due To Maximum STOP Time Windows Which has Now Been Increased to 3 Million (Doc ID 1476913.1)

Last updated on MARCH 20, 2019

Applies to:

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

Symptoms

Users are not able to connect the planner clients to the server to see the current plan. When starting ORS client, the login appears to work but no plan is shown to users. ORS does not appear to be starting correctly following 2 attempted restarts this morning.

We had about 38000 lines of errors stating:
<HOSTNAME> 21/03/12 11:33:10.62 recv RMGWY:0077 RMGWY:1067 >>ERROR|||STOP_TW||1075208AB/T1-TW20110501083000||||||Unable to insert. Cannot exceed MAXIMUM of depot time windows<<
<HOSTNAME> 21/03/12 11:33:10.62 Error: STOP <1075208AB/T1-TW20110501083000> - Unable to insert. Cannot exceed MAXIMUM of depot time windows
<HOSTNAME> 21/03/12 11:33:10.62 Inserted record <STOP:1075208AB/T1-TW20110501083000:Unable to insert. Cannot exceed MAXIMUM of depot time windows> into table

We recently loaded approx 10,000 new stops to ORS.  The error of the depot time windows seemed to start during this time. The ORS system was restarted as part of our normal weekly restart but the problem continued.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.