Typical Recovery Catalog Space Requirements for 1 Year

To create the recovery catalog schema in the recovery catalog database:

Start SQL*Plus and connect with administrator privileges to the database containing the recovery catalog. In this example, the database is catdb.

Create a user and schema for the recovery catalog. For example, you could enter the following SQL statement

CREATE USER rco IDENTIFIED BY password  TEMPORARY TABLESPACE temp   DEFAULT TABLESPACE tools  QUOTA UNLIMITED ON tools; 

Grant the RECOVERY_CATALOG_OWNER role to the schema owner. This role provides the user with all privileges required to maintain and query the recovery catalog.

GRANT RECOVERY_CATALOG_OWNER TO rco; 

To create the recovery catalog:

Start RMAN and connect to the database that will contain the catalog. Connect to the database as the recovery catalog owner.

Run the CREATE CATALOG command to create the catalog. The creation of the catalog can take several minutes. If the catalog tablespace is this user’s default tablespace, then you can run the following command:

RMAN> CREATE CATALOG; 

You can specify the tablespace name for the catalog in the CREATE CATALOG command. For example:

RMAN> CREATE CATALOG TABLESPACE cat_tbs; 

You can check the results by using SQL*Plus to query the recovery catalog to see which tables were created:

SQL> SELECT TABLE_NAME FROM USER_TABLES; 

Registering a Database in the Recovery Catalog

About Standby Database Registration

In a Data Guard environment, the primary and standby databases share the same DBID and database name. To be eligible for registration in the recovery catalog, each database in the Data Guard environment must have different DB_UNIQUE_NAME values. The DB_UNIQUE_NAME parameter for a database is set in its initialization parameter file.

If you use RMAN in a Data Guard environment, then you can use the REGISTER DATABASE command only for the primary database. You can use the following techniques to register a standby database in the recovery catalog:

• When you connect to a standby database as TARGET, RMAN automatically registers the database in the recovery catalog.

• When you run the CONFIGURE DB_UNIQUE_NAME command for a standby database that is not known to the recovery catalog, RMAN automatically registers this standby database if its primary database is registered.

# rman TARGET / CATALOG rco@catdb; 

STARTUP MOUNT; 

REGISTER DATABASE; 

REPORT SCHEMA;  Report of database schema for database with db_unique_name TRGT  List of Permanent Datafiles=========================== File Size(MB)   Tablespace       RB segs Datafile Name ---- ---------- ---------------- ------- ------------------- 1        307200 SYSTEM             NO    /oracle/oradata/trgt/system01.dbf 2         20480 UNDOTBS            YES   /oracle/oradata/trgt/undotbs01.dbf 3         10240 CWMLITE            NO    /oracle/oradata/trgt/cwmlite01.dbf 4         10240 DRSYS              NO    /oracle/oradata/trgt/drsys01.dbf 5         10240 EXAMPLE            NO    /oracle/oradata/trgt/example01.dbf 6         10240 INDX               NO    /oracle/oradata/trgt/indx01.dbf 7         10240 TOOLS              NO    /oracle/oradata/trgt/tools01.dbf 8         10240 USERS              NO    /oracle/oradata/trgt/users01.dbf  List of Temporary Files ======================= File Size(MB) Tablespace           Maxsize(MB) Tempfile Name ---- -------- -------------------- ----------- -------------------- 1    200      TEMP                 32767       /oracle/oradata/trgt/tbs_tmp.dbf