RMAN recovery catalog Is another database which is on a separate server and which will save only the details of your backups in terms of metadata of the backup. Whenever you trigger the backup, RMAN will Update the information in the control file. Your control files can store the backup details for the last 30 days only which is the default 30 days retention period. Suppose you want to have the details of the backups which are taken before 30 days. The recovery catalog will help you in this case to store the history backup details. - It helps in database recovery when you lose the control file - You can write RMAN scripts in recovery catalog and save them - You can use recovery catalog for backups reporting also - You can store RMAN scripts in recovery catalog - Cloning with PITR (Point in time recovery) becomes easier as the recovery catalog knows which Control file is required - Store long term backup history - RMAN stores the backup information into the control file - If we lose control file, we lose all the backup information - Even though the backups are available, they are not usable. If you lose the control file, the backups are of no use as Oracle or RMAN doesn’t know which backup belongs to which database. The reason behind this is the information is stored in the control file which you lost. To resolve all the above three issues, we use recovery catalog. To resolve all the above three issues, we use recovery catalog. - Recovery catalog is a separate database that stores backup information - One recovery catalog can store multiple target database backup information - You don’t have to create multiple recovery catalog for multiple target databases. You can create one recovery catalog database for all the databases or servers You don’t have to create multiple recovery catalog for multiple target databases. You can create one recovery catalog database for all the databases or servers To resolve all the above three issues, we use recovery catalog.

You don’t have to create multiple recovery catalog for multiple target databases. You can create one recovery catalog database for all the databases or servers - Create a default tablespace under prim database which will be used for backup information storage - Create a default tablespace under prim database which will be used for backup information storage - Create a default tablespace under prim database which will be used for backup information storage - , Create a user which will be used to connect recovery catalog and store backup information. We will create the user testuser to connect to the recovery catalog. This user testuser will store the information into rmantbs tablespace. - add tns entry details of catalog server on target server.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

SQL> create tablespace rmantbs datafile '/u01/app/oracle/oradata/prim/rmantbs01.dbf' size 50mb;

SQL> create user testuser identified by testuser default tablespace rmantbs temporary tablespace temp;
Grant permissions to testuser user
SQL> grant connect,resource,recovery_catalog_owner to testuser;

prim =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.50)(PORT = 1521)
)
(CONNECT_DATA =
(SERVICE_NAME = prim)
)
)

SQL> create user testuser identified by testuser default tablespace rmantbs temporary tablespace temp;
Grant permissions to testuser user
SQL> grant connect,resource,recovery_catalog_owner to testuser;