Database Reference
In-Depth Information
Recreating the Recovery Catalog Schema
The first thing we need to do is create a new recovery catalog from scratch. We demon-
strated how to do this earlier in this chapter in the section called “Creating the Recovery
Catalog User and Schema Objects.”
Once the recovery catalog user and schema has been created (or recreated if you prefer),
you will need to register each database that is to be stored in the recovery catalog with the
newly created recovery catalog. During the registration process, the recovery catalog will be
fully synchronized with the target database control file. If you are sure that all of the RMAN
backup related metadata is in the control file of the target database then this would be all you
need to do to recover a lost recovery catalog.
Cataloging Missing Records in the Recovery Catalog Schema
It's very possible that records that were in the recovery catalog will not be in the control
file. They might have been overwritten at some point in time. It's also possible that archival
backup records will be missing. There can be many reasons why existing backups stored in
the recovery catalog would not be in the target database control file.
In the case where records are missing from the control file and/or the recovery catalog, you
can use the
RMAN CATALOG
command to add additional records to the recovery catalog and the
database control file.
The
RMAN CATALOG
command is very powerful. With the
CATALOG
command you can
catalog these kinds of backup related files:
■
database backups
■
archive log backups
■
and control file backups
■
RMAN database image copies
■
Non RMAN created database file image copies
When manually add backups using the
CATALOG
command, you can add backups that
are either on disk or that were made through the SBT interface (i.e., tape). You will need to
know the name and location of the file that you want to catalog.
If your backup files are on disk (but not the Fast Recovery Act (FRA), then you can
simply have RMAN catalog the entire directory full of RMAN files. This is done using the
CATALOG
command and including the
START WITH
parameter.
For example, if all of the missing backup set files are in the
c:\backup\oldbackups
directory, you would first connect to the target database and the recovery catalog. Then
you would use the
CATALOG
command to register these backup files in the recovery catalog,
as seen here:
RMAN> Catalog start with 'c:\backup\oldbackups' noprompt;
If your backup files are on tape, then you will need to know how to properly reference
their location when using the
CATALOG
command. The format you would use is very specific
to each vendor that uses the SBT interface. Sometimes it's easier to just copy all of the backup
files from tape to a disk device and catalog them from that device, assuming you have enough
Search WWH ::
Custom Search