CPU Consumption Of Queue Monitor Processes Increases when using Retention
(Doc ID 343282.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.3 [Release 10.1 to 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.
Queue Monitor process consuming large amounts of CPU and inefficiently removing processed messages
when high message volumes and retention are used in a single-consumer queue table.
Generating 10046, level 12 tracing for the relevant queue monitor process shows that the most inefficient and resource consuming sql statement is of the form
select min(time_manager_info) from <USER.QUEUE_TABLE_NAME> where state not in (:2, :3)
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