Advanced Queueing objects left invalid after executing DBMS_AQADM.PURGE_QUEUE_TABLE with a null condition or performing a shrink
(Doc ID 1523068.1)
Last updated on JUNE 22, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 11.2.0.4 [Release 10.2 to 11.2]Oracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Objects associated with a multi-consumer queue table are left invalidated when dbms_aqadm.purge_queue_table is executed with a null condition which effectively truncates the queue table and the relevant associated IOTS/tables.
These invalid objects can be the evaluation context, rulesets or queues themselves.
However, the queue can still be successfully used for Advanced Queueing (AQ) enqueue/dequeue operations after the purge but not all the objects automatically revalidate.
The same issue can be observed when performing an
alter table <queue_table> shrink;
operation.
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 |