Configure RMAN RECOVERY CATALOG

Configure RMAN RECOVERY CATALOG

Oracle's RMAN configuration information is stored in the control file of the target database by default. You can also configure a recovery catalog server to store the information. The following is a comparison between the control file and recovery features.
Control file:
-Simpler administration
-Default
Recovery catalog:
-Replicates control file data
-Has room for more data
-Can service discovery targets
-Can store RMAN scripts
RMAN repository data is always stored in the control file of the target database. But it can also be stored in a separate database, called a recovery catalog.
A recovery catalog preserves backup information in a separate database, which is useful in the event of a lost control file. this allows you to store a longer history of backups than what is possible with a control file-based repository. A single recovery catalog is able to store information for multiple target databases. the recovery catalog can also hold RMAN stored scripts, which are sequences of RMAN commands for common backup tasks. centralized storage of scripts in the recovery catalog can be more convenient than working with command files.
Usage of a separate recovery catalog database is not recommended for small installations where administration of a separate recovery catalog database wocould be burdenso

The following shows how to restore the directory configuration, where jy is the catalog Database and the test database is the test database.
1. create user/table space and authorization (I have used users table space to create a new table space here)
SQL> create user rman identified by "rman"
2 default tablespace users
3 temporary tablespace temp
4 quota unlimited on users;

User created.

SQL> grant recovery_catalog_owner to rman;

Grant succeeded.

SQL> conn rman/rman
Connected.
SQL> select count (*) from user_objects;

COUNT (*)
----------
0

2: Create a recovery directory
[Oracle @ jingyong1 admin] $ rman catalog rman/rman @ jy

Recovery Manager: Release 10.2.0.5.0-Production on Sun Feb 1 21:22:31 2015

Copyright (c) 1982,200 7, Oracle. All rights reserved.

Connected to recovery catalog database

RMAN> create catalog;

Recovery catalog created

SQL> conn rman/rman
Connected.
SQL> select count (*) from user_objects;

COUNT (*)
----------
194

We can see that there are 194 objects in the rman user.

3: Add a tns service name
[Oracle @ oracle11g admin] $ vi tnsnames. ora

Jy =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.11) (PORT = 1521 ))
)
(CONNECT_DATA =
(SERVICE_NAME = jy)
)
)

 

4: register the target database and synchronize the catalog and control files.
[Oracle @ oracle11g admin] $ rman target sys/zzh_2046 @ test catalog rman/rman @ jy

Recovery Manager: Release 10.2.0.5.0-Production on Sun Feb 1 21:25:25 2015

Copyright (c) 1982,200 7, Oracle. All rights reserved.

Connected to target database: TEST (DBID = 2155613261)
Connected to recovery catalog database

RMAN> register database;

Database registered in recovery catalog
Starting full resync of recovery catalog
Full resync complete

RMAN> resync catalog;

Starting full resync of recovery catalog
Full resync complete

RMAN> list incarnation;

List of Database Incarnations
DB Key Inc Key DB Name db id status Reset SCN Reset Time
-------------------------------------------------------------
1 10 TEST 2155613261 PARENT 1 30-JUN-05
1 11 TEST 2155613261 PARENT 446075 05-SEP-14
1 12 TEST 2155613261 PARENT 2849317 27-JAN-15
1 13 TEST 2155613261 PARENT 2880152 27-JAN-15
1 2 TEST 2155613261 CURRENT 3017109 01-FEB-15

-------------------------------------- Recommended reading --------------------------------------

RMAN: Configure an archive log deletion policy

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption

-------------------------------------- Split line --------------------------------------