Casting AQ$QUEUE_TABLE Enqueue and Dequeue Time Values To SESSIONTIMEZONE causes Reporting and Message Processing issues
Last updated on NOVEMBER 20, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 220.127.116.11 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Two symptoms can be observed:
The most common symptom observed is that the enqueue time (ENQ_TIME) and dequeue time (DEQ_TIME) values in the internally create AQ$QUEUE_TABLE view report values are in sync with the session time zone but are out of sync with the enq_time reported in the underlying queue table after a Daylight Time Saving change. However, messages are processed as normal.
In RAC environments this issue can affect message processing if the nodes in the cluster have been started with different unix environment variable TZ settings. Messages enqueued via different nodes will then have different enqueue times calculated for them even if they have been enqueued at the same time due to the offset value generated by kwqa_3gl_GetOSTimezone, which can be checked via:
select sys.dbms_aqadm_syscalls.kwqa_3gl_GetOSTimezone from dual;
returning different offset settings for different nodes.
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