Step by Step - How to Create And Configure RMAN Recovery Catalog Database

By -



Purpose of the Recovery Catalog

A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. Typically, you store the catalog in a dedicated database. A recovery catalog provides the following benefits:
  • A recovery catalog creates redundancy for the RMAN repository stored in the control file of each target database. The recovery catalog serves as a secondary metadata repository. If the target control file and all backups are lost, then the RMAN metadata still exists in the recovery catalog.
  • A recovery catalog centralizes metadata for all your target databases. Storing the metadata in a single place makes reporting and administration tasks easier to perform.
  • A recovery catalog can store metadata history much longer than the control file. This capability is useful if you must do a recovery that goes further back in time than the history in the control file. The added complexity of managing a recovery catalog database can be offset by the convenience of having the extended backup history available.
Some RMAN features function only when you use a recovery catalog. For example, you can store RMAN scripts in a recovery catalog. The chief advantage of a stored script is that it is available to any RMAN client that can connect to the target database and recovery catalog. Command files are only available if the RMAN client has access to the file system on which they are stored.
A recovery catalog is required when you use RMAN in a Data Guard environment. By storing backup metadata for all primary and standby databases, the catalog enables you to offload backup tasks to one standby database while enabling you to restore backups on other databases in the environment.

Basic Concepts for the Recovery Catalog

The recovery catalog contains metadata about RMAN operations for each registered target database. When RMAN is connected to a recovery catalog, RMAN obtains its metadata exclusively from the catalog. The catalog includes the following types of metadata:
  • Datafile and archived redo log backup sets and backup pieces
  • Datafile copies
  • Archived redo logs and their copies
  • Database structure (tablespaces and datafiles)
  • Stored scripts, which are named user-created sequences of RMAN commands
  • Persistent RMAN configuration settings

Database Registration

The process of enrolling of a database in a recovery catalog for RMAN use is called registration. The recommended practice is to register every target database in your environment in a single recovery catalog. For example, you can register databases prod1, prod2, and prod3 in a single catalog owned by catowner in the database catdb.

Creating a Recovery Catalog

Configuring the Recovery Catalog Database

When you use a recovery catalog, RMAN requires that you maintain a recovery catalog schema. The recovery catalog is stored in the default tablespace of the schema. The SYS user cannot be the owner of the recovery catalog.
Decide which database you will use to install the recovery catalog schema, and also how you will back up this database. Also, decide whether to operate the catalog database in ARCHIVELOG mode, which is recommended.

Steps to Create a RMAN Catalog User

  1. Suppose you have create a oracle database or you already have a database created. We are considering catdb as our Recovery Catalog Database. Connect to database catdb as show below. 
    •  C:\set ORACLE_SID=catdb  
 C:\sqlplus / as sysdba
  2. Create a user and schema for the recovery catalog.
    •  SQL> CREATE USER rman_rc IDENTIFIED BY rman_rc  
      DEFAULT TABLESPACE users  
      QUOTA UNLIMITED ON users;
  3. 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.
    •  SQL> grant RECOVERY_CATALOG_OWNER TO rman;
  4.  After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. The command creates the catalog in the default tablespace of the catalog owner.
    •  C:\rman catalog rman_rc/rman_rc  
 RMAN> CREATE CATALOG;
  5. You can now connect to the catalog user from sqlplus to check the tables and view names created by the above command.
    •  C:\set ORACLE_SID=catdb  
 C:\sqlplus rman_rc/rman_rc  
 SQL> select * from tab;

Registering a Database with the REGISTER DATABASE Command

  1. The first step in using a recovery catalog with a target database is registering the target database in the recovery catalog. 
  2. Start RMAN and connect to a target database and recovery catalog. The recovery catalog database must be open. For example, issue the following command to connect to the catalog database with the net service name catdb as user rman_rc (who owns the catalog schema)
    •  C:\set ORACLE_SID=orcl  
 C:\rman TARGET / CATALOG rman_rc/rman_rc@catdb
  3. Register the target database in the connected recovery catalog. RMAN creates rows in the catalog tables to contain information about the target database, then copies all pertinent data about the target database from the control file into the catalog, synchronizing the catalog with the control file. 
    •  RMAN> REGISTER DATABASE;
  4. Verify that the registration was successful by running REPORT SCHEMA 
    •  RMAN> REPORT SCHEMA; 
Reference Source :- docs.oracle.com

Comments

Post a Comment

Popular posts from this blog

Oracle Architecture - Explained In Detailed - Administration I

By -
Image
Figures shown in these notes are from Oracle® Database Concepts 11 g Release 2 Objectives These notes introduce the Oracle server architecture.   The architecture includes physical components, memory components, processes, and logical structures. Primary Architecture Components The figure shown above details the Oracle architecture. Oracle server :   An Oracle server includes an Oracle Instance and an Oracle database .   ·         An Oracle database includes several different types of files:   datafiles, control files, redo log files and archive redo log files.   The Oracle server also accesses parameter files and password files.   ·         This set of files has several purposes.   o    One is to enable system users to process SQL statements.   o    Another is to improve system performance.   o    Still another is to ensure the database can be recovered if there is a software/hardware failure. ·         The database server must manage large amo
Read more

Oracle Database SQL - Practise - Question - Scott Schema Examples

By -
Image
Oracle SQL Practice Questions for Students All Question are Based on Scott Schema Exhibits EMP TABLE Exhibits DEPT TABLE Exhibits SALGRADE TABLE Question 1) Display all the records in emp table? 2) Display all the records in emp table where employee belongs to deptno 10? 3) Display all the records in emp table where employee does not belong to deptno 30? 4) Display total number of records in Emp table? 5) Display emp table with salary descending order? 6) Display first five records in employee table? 7) Display all the records in emp table order by ascending deptno, descending salary? 8) Display all employees those who were joined in year 1981? 9) Display COMM in emp table. Display zero in place of null. 10) Display the records in emp table where MGR in 7698,7566 and sal should be greater then 1500 11) Display all employees where employees hired before 01-JAN-1981 12) Display all employees with
Read more

Step by Step - How to resolve redo log file corruption using ALTER DATABASE CLEAR UNARCHIVED LOGFILE command

By -
Image
Connect to sys using sqlplus in admin command prompt Check whether your database is in archive log mode or not. Run command ARCHIVE LOG LIST. It will show you the following details: It is always preferable to have your database in archive log mode. The reason being if your database is in archive log mode you can recover from all committed changes in the event of an OS or disk failure. This query will display the path of redo log files, their group and their status. It is always recommended to have a minimum of two members in one group. As you can see I have only 1 member in group 6 whose current status is INACTIVE. I intentionally have 1 member to generate a scenario for the sake of this practical. Now go to the specified path where the redo log member of group 6 is located and open it in a notepad. It will show some symbolic data. Delete couple of lines and save it the original location which is the one we got as a result of query. Why did we do the above step i.
Read more