Dequeue by Condition Statement Has High Buffer Gets, Elapsed Time and CPU Time
Last updated on NOVEMBER 04, 2014
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 11.2]
Information in this document applies to any platform.
Dequeuing sessions that are using a condition are consuming very high Buffer Gets, elapsed time, and CPU time. A statement similar to the following is seen to be consuming these resources:
where <SCHEMA> is the queue table owner, <QUEUE_TABLE_NAME> is the queue table name, and <dequeue condition> is the condition specified in the dequeue_options.deq_condition parameter in the DBMS_AQ.DEQUEUE procedure used to dequeue messages from the queue table.
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