Enqueue Time For Advanced Queueing Messages can be Different from Sysdate
(Doc ID 252685.1)
Last updated on JANUARY 11, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.1.0.7 [Release 9.2 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
After changing the operating system clock and not restarting the database subsequent messages do not get enqueued or dequeued with a value consistent with sysdate.
The enqueue time in the enq_time column of the queue table does not match the sysdate of the database when a message is enqueued.
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 |
| Cause |
| Solution |
| References |