Procedures to Remove Orphan AQ Objects Which Fail to Drop via DBMS_AQADM
(Doc ID 236898.1)
Last updated on JUNE 07, 2021
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 8.1.7 to 9.2]
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.
The purpose of this article is to provide procedures, which remove damaged Advanced Queuing (AQ)tables and Queues for pre-10g databases. By damaged we mean that the AQ objects cannot be removed via the means discussed in the Supported Method for dropping AQ Tables section below.
This article is intended for anyone who needs to remove damaged AQ objects in pre-10g databases. From 10.1 onwards the drop_queue_table procedure has been made more robust and should handle most if not all situations that the following procedures handle when using the force option as discussed below.
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
|Typical scenarios when a queue table/queue or user cannot be dropped|