Chat now with support
Chat with Support

NetVault Plug-in for Oracle 11.2 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle® Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the Plug-in with Oracle® RAC Using the Plug-in in a failover cluster environment Using the plug-in with Oracle® Data Guard Troubleshooting

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. SYS cannot be the owner of the Recovery Catalog. Decide which database you want to use to install the Recovery Catalog schema. Quest recommends that you create a separate database for the Recovery Catalog and run the catalog database in ARCHIVELOG mode.

Next, allocate space to be used by the catalog schema. The size of the Recovery Catalog schema depends on the number of databases managed by the catalog. The schema also grows as the number of archived redo log files and backups for each database increases. For more information on sizing the Recovery Catalog schema, see Planning the Size of the Recovery Catalog Schema in the Oracle® Database Backup and Recovery Advanced User’s Guide.

Creating the Recovery Catalog owner

After choosing the Recovery Catalog database and creating the necessary space, perform the following steps to create the owner of the Recovery Catalog and grant this user the necessary privileges:

1
Start SQL*Plus, and connect with administrator privileges to the database that will contain the Recovery Catalog.
sqlplus SYS/<password>@<connect_identifier> AS SYSDBA
2
Create a user and schema for the Recovery Catalog.
For example, enter:
CREATE USER rman IDENTIFIED BY <password>
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE tools
QUOTA UNLIMITED ON tools;
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.
GRANT RECOVERY_CATALOG_OWNER TO rman;
4
Grant the CONNECT role to the rman user.
GRANT CONNECT TO rman;

Creating the Recovery Catalog

After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. This command creates the catalog in the default tablespace of the catalog owner.

1
Connect to the database that will contain the catalog as the catalog owner.
For example:
> rman CONNECT CATALOG rman/<password>@<connect_identifier_for_catalog>
2
Run the CREATE CATALOG command to create the catalog.
The creation of the catalog can take several minutes.
If the catalog tablespace is this user’s default tablespace, you can run this command:
CREATE CATALOG;
You can also specify the tablespace name for the catalog in the CREATE CATALOG command. For example:
CREATE CATALOG TABLESPACE <tablespace_name>;

Registering the target database

The first step in using a Recovery Catalog with a target database is registering the database in the Recovery Catalog.

1
After making sure that the Recovery Catalog database is open, connect RMAN to the target database and Recovery Catalog database.
For example, issue the following command to connect to the catalog database.
> rman TARGET / CATALOG rman/<password>@<connect_identifier_for_catalog>
2
If the target database is not mounted, mount or open it:
STARTUP MOUNT;
3
Register the target database in the connected Recovery Catalog:
REGISTER DATABASE;
RMAN creates rows in the catalog tables to contain information about the target database. RMAN then copies all pertinent data about the target database from the Control File into the catalog, synchronizing the Catalog with the Control File.
4
Verify that the registration was successful.
REPORT SCHEMA
Registering multiple databases in a Recovery Catalog

You can register multiple target databases in a single Recovery Catalog, if they do not have duplicate DBIDs. RMAN uses the DBID to distinguish one database from a different database.

In a Data Guard environment, only the primary database is registered in the Recovery Catalog.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating