Databases Reference
In-Depth Information
In the previous command, you must specify the connection string for the source catalog whose metadata you
want to import into the destination catalog. Issue the
list incarnation
command again to ensure that all three
databases are now part of the single consolidated recovery catalog:
RMAN> list incarnation;
You'll also find that there are no databases registered in the source database any longer, when you issue the
list incarnation
command in the source recovery catalog.
You don't see any databases registered in the source database, since RMAN automatically unregisters all
databases from the source recovery catalog after importing the contents of that catalog into the destination recovery
catalog. If you don't want RMAN to unregister the databases from the source catalog after importing the metadata
for the databases registered in that catalog, issue the following
import catalog
command, with the
no unregister
option:
RMAN> import catalog rman11/rman11@eleven no unregister;
In cases where you want to re-create a recovery catalog from a source catalog, you will not want to unregister
all databases from the source catalog.
How It Works
Importing a catalog into another and merging it with the destination catalog all takes place without connecting to a
target database. You simply need to connect to the source and destination recovery catalogs with the RMAN client.
The
import catalog
command will import the metadata for all the databases that are currently registered in the
source catalog schema into the destination catalog schema. If you'd rather import a specific database(s), you can do
so using the following variation on the
import catalog
command wherein you specify the DBID or database name
of the database you want to import:
RMAN> import catalog rman11/rman11@eleven dbid = 123456, 123457;
RMAN> import catalog rman11/rman11@eleven db_name = testdb, mydb;
If a database is registered in both the source and destination target recovery catalogs, first unregister that
database from one of the catalogs before proceeding. You can't perform an import when a database is simultaneously
registered in both the source and destination catalogs.
You
can issue the
import catalog
command only if the source database's version is identical to the version of
the RMAN client you're using. If the source recovery catalog schema belongs to an older version, upgrade that catalog
schema first using the
upgrade catalog
command.
Moving the Recovery Catalog to Another Database
Problem
You want to move a recovery catalog from one database to another.
