Dropping the Recovery Catalog

If you do not want to maintain a recovery catalog, then you can drop the recovery catalog schema from the tablespace. The DROP CATALOG command deletes all information from the recovery catalog. Hence, if you have no backups of the recovery catalog schema, then backups of all target databases managed by this catalog may become unusable. (The control file of the target database will still retain a record of recent backups.)

The DROP CATALOG command is not appropriate for unregistering a single database from a recovery catalog that has multiple target databases registered. Dropping the catalog deletes the recovery catalog record of backups for all target databases registered in the catalog.

To drop the recovery catalog schema:

1. Use RMAN to connect to the target and recovery catalog databases.

   % rman TARGET / CATALOG rman/cat@catdb
   
   

2. Issue the DROP CATALOG command twice to confirm:

   DROP CATALOG;
   
   recovery catalog owner is rman
   enter DROP CATALOG command again to confirm catalog removal
   
   DROP CATALOG;
   

   Note:

   Even after you drop the recovery catalog, the control file still contains records about the backups. To purge RMAN repository records from the control file, re-create the control file.

   See Also:

   Oracle Database Backup and Recovery Reference for DROP CATALOG command syntax, and "Unregistering a Target Database from the Recovery Catalog" to learn how to unregister a database from the catalog