Queue Monitor Auto-Tuning only uses 1 Qmon Slave Process for Persistent Queues
(Doc ID 809383.1)
Last updated on FEBRUARY 11, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206 [Release 10.1 to 11.1]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.
In 10.1 onwards, when using the auto-tuning algorithm of the qmon slave processes, only 1 qmon slave process ever handles persistent queues by default.
This can result in a backlog of PROCESSED messages which are not removed in a timely manner with or without retention being used. In turn this can result in excessive storage consumption.
If enqueue sessions are stopped the PROCESSED messages are removed. In other words the messages are suitable candidates for removal and are just not being removed quickly enough.
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