My Oracle Support Banner

RMAN 11G : Import Catalog (Doc ID 419173.1)

Last updated on MARCH 25, 2021

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

2 Target databases : V110 and DUPLV110
2 RMAN Catalogs in the same catalog database V110
Catalog 1 : Owner RMAN, registered database V110
Catalog 2 : Owner CAT1, registered database DUPLV110
Catalog TNS connection: v110, v102, wrong_v110


Description of the RMAN Import Catalog feature introduced in Oracle 11G.

The new IMPORT CATALOG command allows one catalog schema to be imported into another either the whole schema or just the metadata for specific databases in the catalog.


Intended audience are DBA's who are supporting Oracle databases and use RMAN as Backup & Recovery tool.

Basic knowledge of RMAN is required.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 1. Environment
 2. Examples
 3. From the trace file
 4. Known Issues

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.