Databases Reference
In-Depth Information
Solution
You can move a recovery catalog to a different database from the present recovery catalog database by using the
import catalog
command. Here are the steps to move a recovery catalog:
1.
Create a new recovery catalog in the target database, but don't register any databases in it.
Use the
import catalog
command in RMAN after connecting to the target database:
2.
$ rman
RMAN> connect catalog rman/rman@target_db
RMAN> import catalog rman11/rman11@source_db;
The
import catalog
command will import the source recovery catalog contents into the target recovery catalog.
How It Works
Moving a recovery catalog to another database is similar to merging recovery catalogs discussed in the previous
recipe, since both operations make use of the
import catalog
command to import a recovery catalog from one
database to another.
Creating a High-Availability Recovery Catalog
Problem
You have registered a large number of databases in a single recovery catalog and want to ensure that the recovery
catalog is always available to perform backup and recovery tasks. That is, you want a high-availability solution for
the RMAN recovery catalog.
Solution
The solution is to maintain multiple, redundant recovery catalogs. If you're using the recovery catalog to manage
the backup and recovery tasks for a large number of production databases, maintaining high availability becomes
critical. You can ensure high availability of the recovery catalog just as you would any other Oracle database—by using
a
standby
recovery catalog instance. In the case of recovery catalogs, however, you really don't use a special standby
database for the alternate recovery catalog instance—you simply maintain a
secondary recovery catalog
that can take
over from the primary recovery catalog in the event disaster strikes.
Here's a simple outline of the strategy for using a standby recovery catalog:
1.
Create a secondary recovery catalog in a separate Oracle database.
2.
Register all databases—all that you have registered in your primary catalog—in the
secondary recovery catalog.
3.
The primary recovery catalog is synchronized automatically during the normal backups of
the target databases.
Synchronize the secondary recovery catalog manually with the
resync catalog
command
after connecting to each of the target databases registered in the catalog.
4.
5.
Switch to the secondary catalog as the primary recovery catalog when necessary after
resynchronizing it first. Switching to the secondary catalog is as easy as can be. Simply
connect to that catalog instead of to the primary one. The secondary catalog will now be
your primary catalog.
