Dequeue by Condition Statement Has High Buffer Gets, Elapsed Time and CPU Time
(Doc ID 1276457.1)
Last updated on DECEMBER 16, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 9.2 to 11.2]
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.
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.
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