Create RMAN catalog for physical backup

1. scenario description;
Catalog database 192.168.1.206: 1521 grid
Target database 192.168.1.201: 1521 ql
2. Create the rman tablespace on the catalog database
 
SQL> create tablespace rman datafile '/u01/app/Oracle/oradata/gird/rman. dbf' size 500 m autoextend on next 100 m maxsize unlimited;
Tablespace created.
 
3. Create an rman user on the catalog database
 
SQL> create user rman identified by rman default tablespace rman quota 500 m on rman;
User created.
 
4. grant permissions to the rman user on the catalog database
SQL> grant connect, resource to rman;
Grant succeeded.
SQL> grant recovery_catalog_owner to rman;
Grant succeeded.
 
5. Modify tnsname. ora on target database
[Oracle @ test admin] $ more tnsnames. ora
RMAN =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.206) (PORT = 1521 ))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = gird.57ql.com)
)
)
6. Register a database
 
[Oracle @ test/] $ rman target/catalogrman/rman @ rman;
Recovery Manager: Release 11.2.0.3.0-Production on Mon Sep 3 16:12:41 2012
Copyright (c) 1982,201 1, Oracle and/or its affiliates. All rights reserved.
Connected to target database: QL (DBID = 2286587371)
Connected to recovery catalog database
 
RMAN> create catalog tablespace "RMAN ";
Recovery catalog created
 
RMAN> register database;
Database registered in recovery catalog
Starting full resync of recovery catalog
Full resync complete
 
7. Back up the database
RMAN> backup database;
Finished Control File and SPFILE Autobackup at 03-SEP-12
RMAN> exit

8. Summary
Using catalog database to store rman backup metadata is very common in the production environment and is highly secure. The reponsitory database of grid control can be integrated with the catalog database.