QMON does not perform space management operations on the dequeue IOT in Locally Managed Tablespaces using ASSM or when using FREELIST GROUPs
(Doc ID 267137.1)
Last updated on FEBRUARY 26, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 9.0.1.0 to 11.1.0.7 [Release 9.0.1 to 11.1]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.
Symptoms
How the problem may manifest itself will depend on the amount of Advanced Queueing (AQ) activity in the database and on the configuration of the Queues.
The symptoms may include but are not limited to the following:
1. It may be observed as a space management issue in that the segment associated with the dequeue IOT/index, AQ$_< QUEUE_TABLE_NAME >_I, gradually grows in size. (AQ$_ < QUEUE_TABLE_NAME >_I will be an IOT for a Multi consumer queue table and an index for a Single consumer queue table.)
2. Dequeue performance may be seen to degrade over time due to the increasing size of the segment associated with the IOT/index.
3. In 10850 level 2 queue monitor tracing entries of the form kwqitremb: Skipping <OWNER>.AQ$_ <QUEUE_TABLE_NAME > _I will be recorded.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |