A Dequeue Condition fails to work properly after a Daylight Savings Time Change
(Doc ID 429630.1)
Last updated on FEBRUARY 01, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
After a daylight savings time change a dequeue condition which uses the enqueue time of the message in comparison with SYSDATE is failing to work properly as the enqueue time is now offset from the time reported by SYSDATE by 1 hour.
The enqueue_time reported by querying the AQ$QUEUE_TABLE view itself will also be out of sync with that reported by SYSDATE.
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 |