IMPORT CATALOG is a new feature of RMAN in Oracle 11g. We can move or merge schemas of different RECOVERY CATALOG of different databases into a centralized repository.
In a nut shell It is nothing but importing a CATALOG from one database to another, or in other words, “moving” or “migrating” CATALOG.
SOURCE DATABASE – GGDB1
TARGET DATABASE – GGDB2
ORACLE VERSION – 22.214.171.124.0
OS VERSION – Linux 6.0 X86_64
The below scenario describes the steps to move a CATALOG from GGDB1 (Source) to GGDB2 (Target).
In GGDB1 – The catalog is registered.
In GGDB2 – Check the CATALOG for the registered database.
In GGDB2 – Connect to the destination database that will receive the new CATALOG data.
Issue the IMPORT CATALOG command specifying the owner of the source catalog and Check the registered database in the catalog in GGDB2 (Target database).
We can see GGDB1 is also registered to this CATALOG.
In GGDB1 – Check the source catalog (GGDB1) for the registered database.,
On the Source Catalog, the database will be automatically Unregistered after the IMPORT CATALOG.
If you need to retain the catalog on the source side even after the import then a keyword should be added to the IMPORT CATALOG command.
Connect to the RMAN prompt and issue the IMPORT CATALOG command with the keyword NO UNREGISTER.,
Check whether the source database (GGDB1) is registered to the New target catalog database (GGDB2).
Now check on the Source (GGDB1) side whether the imported database exists.
You can clearly see that the database is not Unregistered from the Source side.