AQ MESSAGES ENQUEUED WITH DELAY FOR SHARDED QUEUES STUCK IN WAIT/EXPIRED STATE
(Doc ID 2744701.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
When AQ messages are enqueued with delay for single consumer sharded queues, it is enqueued with WAIT state as expected in 12.2 version. But, it remains in the WAIT state and never changes to READY even after the delay period is over.When the messages are enqueued without delay their status set to READY as expected.
On 19.3 Version of db, the messages enqueued with delay for single consumer sharded queues were enqueued in state EXPIRED and no WAIT State was observed.
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 |