It is always recommended to have the recovery catalog to store RMAN related information. In absence of recovery catalog RMAN stores the information in the database control files. If the target database control files are lost recovery can become difficult if not impossible.Having recovery catalog makes the DBA life easier at the time of critical scenario.
As a best practice make sure to have a separate database for the recovery catalog always .
You have already created a recovery catalog database, and want to create a recovery catalog in that database.
STEP 1 CREATE A DEFAULT TABLESPACE FOR RMAN
Create a default tablespace for the RMAN recovery catalog owner you’re about to create. Otherwise, the system tablespace may be used by default to hold the recovery catalog structures, which is not a good idea. 500MB is good enough space for a medium size database being backed up daily.
Login to SQL with SYSDBA privileges
SYS@rmandb > create tablespace catalogtbs datafile ‘/u03/oracle/DBRMAN/oradata/rmandb/catalogtbs_01.dbf’ size 500M;
STEP 2 CREATE THE RECOVERY CATALOG OWNER
You need to create a rman user with default tablespace which we created in the previous step.
SYS@rmandb > create user rman identified by rman
temporary tablespace temp
default tablespace catalogtbs
quota unlimited on catalogtbs;
STEP 3 GRANT ‘recovery_catalog_owner’ PRIVILEGE
You must grant rman user the recovery_catalog_owner privilege in order for it to have the authority to work with the recovery catalog.
SYS@rmandb > grant recovery_catalog_owner to rman;
STEP 4 CREATE THE RECOVERY CATALOG
Connect to the RMAN catalog database by starting up the RMAN client and using the connect catalog command. You must connect as the recovery catalog owner you created in the previous steps.
Recovery Manager: Release 18.104.22.168.0 – Production on Wed Feb 12 17:10:33 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN> connect catalog rman/rman@rmandb
connected to recovery catalog database
RMAN> create catalog;
recovery catalog created
[Post Views: 2597]
You can connect with me on LinkedIn.
Latest posts by Brijesh Gogia (see all)
- Performance Tuning Basics 16 : Using SQL Tuning Health-Check Script (SQLHC) - April 1, 2018
- Physical and Logical Block Corruption in Oracle Database - March 10, 2018
- Performance Tuning Basics 15 : AWR Report Analysis - February 6, 2018