ORS Client and Database Out Of Sync With 'Timeout waiting for missing postbox expired' Due To Incorrect DEAD_PROC_TIMEOUT Parameter (Doc ID 1469164.1)

Last updated on NOVEMBER 12, 2015

Applies to:

Oracle Real-Time Scheduler - Version 1.12.0 to 1.13.2 [Release 1.12 to 1.13]
Information in this document applies to any platform.

Symptoms

The database and client data are out of sync.  The ORS Database is not reflecting the same number of stops as seen in the ORS Planner Client.  There are also error messages relating to the Postbox logged in the Resource Manager Gateway stating:

 

Changes

In some cases this issue can be introduced after a system restart, after introducing new configuration settings in the database or .cfg files or, after changes to the database configuration (especially when involving RAC as discussed in Note:1343804.1

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