PROCESSED Messages Left in Queue and Not Cleaned out by QMON
(Doc ID 1529141.1)
Last updated on JULY 26, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Message in status PROCESSED not removed from queue.
If the time between dequeue of the message and COMMIT is more than some value,
completely processed message isn't removed from queue.
In our tests when delay period makes 15 seconds the message normally is removed.
If the time delay makes 45 seconds the message isn't removed from queue and
remains in it in state PROCESSED.
TEST CASE:
=============
OUTPUT:
Equeue message: A863053DE9E5F5CFE0408D0A5F9B6558
Dequeue message: A863053DE9E5F5CFE0408D0A5F9B6558
Message status: A863053DE9E5F5CFE0408D0A5F9B6558 - PROCESSED
PL/SQL procedure successfully completed.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |