Queue Monitor Auto-Tuning only uses 1 Qmon Slave Process for Persistent Queues
Last updated on JULY 16, 2009
Applies to:Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 184.108.40.206
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms