Skip Headers
Oracle® Database Backup and Recovery Reference
11g Release 1 (11.1)

Part Number B28273-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF



Use the DROP CATALOG command to remove the recovery catalog or a virtual private catalog.

See Also:

Oracle Database Backup and Recovery User's Guide to learn how to drop the recovery catalog


Execute this command only at the RMAN prompt.

You must be connected to the recovery catalog schema or virtual private catalog schema with the CATALOG command-line option or the CONNECT CATALOG command. The recovery catalog database must be open.

You do not have to be connected to a target database.

Usage Notes

After you execute DROP CATALOG, RMAN prompts you to enter the command again to confirm that you want to perform the operation.

A base recovery catalog is created with CREATE CATALOG, whereas a virtual private catalog is created with CREATE VIRTUAL CATALOG. To drop the base recovery catalog, execute DROP CATALOG while connected to the recovery catalog database as the recovery catalog owner.


When you drop the base recovery catalog, all RMAN metadata is removed from the recovery catalog. Any backups recorded in the recovery catalog but not in a target database control are not usable by RMAN.

To drop a virtual private catalog, execute the DROP CATALOG command while connected to the virtual private catalog. When connected to a virtual private catalog, the DROP CATALOG command does not remove the base recovery catalog itself, but only drops the synonyms and views that refer to the base catalog.

Note that you must use a different technique to drop a virtual catalog when using a 10.2 or earlier release of the RMAN client. Before dropping the virtual private catalog, the user must connect to the recovery catalog database as the virtual private catalog owner and execute the following PL/SQL procedure (where base_catalog_owner is the database user who owns the base recovery catalog):


If you drop the base recovery catalog but not the virtual private catalog, then the virtual catalog is unusable. However, if a dedicated database user owns the virtual private catalog, then you can execute DROP USER ... CASCADE to remove the virtual catalog.



Description of dropcatalog.gif follows
Description of the illustration dropcatalog.gif


Example 2-68 Dropping a Virtual Private Catalog

Assume that you want to remove the virtual private catalog belonging to database user vpu1, but do not want to drop the base recovery catalog. This example connects to the recovery catalog database as vpu1 and drops the virtual private catalog for this user. The base recovery catalog is not affected by the removal of this virtual private catalog.

RMAN> CONNECT CATALOG vpu1/password@catdb
connected to recovery catalog database
recovery catalog owner is VPU1
enter DROP CATALOG command again to confirm catalog removal
virtual catalog dropped