Last updated on DECEMBER 12, 2011
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.
The issue was found when Planner status values were compared directly with status values in the STOP_SCHED table and differences were found where the two source were out of sync. This issue would also be apparent if statuses reverted to old values after a system restart.
No application level logs show any errors related to the issue.
### Recent Changes ###
We did a DB upgrade from 10g to 22.214.171.124.0. The full system was restarted this morning in attempt to correct the problem.
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