A Dequeue Condition fails to work properly after a Daylight Savings Time Change
Last updated on FEBRUARY 18, 2015
Applies to:Oracle Server - Enterprise Edition - Version 10.1.0.2 to 18.104.22.168 [Release 10.1 to 11.1]
Information in this document applies to any platform.
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.
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