Enqueue Time For Advanced Queueing Messages can be Different from Sysdate

(Doc ID 252685.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Server - Enterprise Edition - Version: to
This problem can occur on any platform.


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.


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