Databases Reference
In-Depth Information
Solution
You can remove a target database's information from a recovery catalog and stop RMAN from tracking a target
database's activity in that catalog by using the
unregister database
command. Here are the steps for unregistering
a database from the recovery catalog:
1.
Connect both to the recovery catalog and to the target database:
[oracle@virtual1 ~]$ rman target / catalog rman/rman@catdb
Recovery Manager: Release 12.1.0.0.2 - Beta on Mon Sep 10 13:05:43 2012
Copyright (c) 1982, 2012, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1316762630)
connected to recovery catalog database
RMAN>
Issue the
unregister database
command to unregister the target database to which
you're currently connected:
2.
RMAN> unregister database;
database name is "ORCL" and DBID is 1316762630
Do you really want to unregister the database (enter YES or NO)? yes
database unregistered from the recovery catalog
RMAN>
RMAN>
You may also explicitly specify the name of the database you want to unregister from the recovery catalog,
along with the
unregister
command, as in
unregister database tenner
, for example.
How It Works
When you unregister a target database from the recovery catalog, the backups pertaining to that database
aren't affected—you now rely on the control file, instead of the recovery catalog, to store the history of those
backups. Just a reminder—prior to the Oracle Database 10
g
release, you were required to execute the
dbms_rcvcat.unregisterdatabase(db_key, db_id)
procedure from SQL*Plus to unregister a database from the
recovery catalog.
Prior to unregistering a database, it's a smart idea to record the complete set of backups known to the recovery
catalog by issuing the commands
list backup summary
and
list copy summary
. Then, if you later decide to
reregister the database, you'll know exactly which backups are not recorded in that database's control file. You'll
need to recatalog those backups. Recipe 6-6 shows you how.
