Advanced Queueing objects left invalid after executing DBMS_AQADM.PURGE_QUEUE_TABLE with a null condition or performing a shrink
Last updated on AUGUST 10, 2015
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 to 18.104.22.168 [Release 10.2 to 11.2]
Information in this document applies to any platform.
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;
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms