2.12 CREATE CATALOG
CREATE CATALOG command to create a base recovery catalog. A virtual private catalog is created automatically when catalog privileges are granted to the virtual private catalog owner.
A base recovery catalog is a database schema that contains RMAN metadata for a set of target databases.
A virtual private catalog is a set of security policies that restrict user access to a subset of a base recovery catalog.
Oracle Database Backup and Recovery User's Guide to learn how to create the recovery catalog
"RMAN Compatibility" to learn about the requirements for the compatibility of the recovery catalog and the other components of the RMAN environment
Execute this command only at the RMAN prompt. RMAN must be connected to the recovery catalog database either through the
CATALOG command-line option or the
CATALOG command, and the catalog database must be open. A connection to a target database is not required.
The recovery catalog owner for the base recovery catalog must be granted the
RECOVERY_CATALOG_OWNER role. The recovery catalog is created in the default tablespace of the recovery catalog owner.
Starting with Oracle Database 12c Release 1 (220.127.116.11), the recovery catalog database must use the Enterprise Edition.
The database user who owns a virtual private catalog must be granted the
CREATE SESSION privilege. Starting with Oracle Database 12c Release 1 (18.104.22.168), virtual private catalogs can be created only when using Oracle Database Enterprise Edition.
If you are creating a virtual private catalog, then the base recovery catalog owner must have used the RMAN
GRANT command to grant either the
REGISTER privilege (see Example 2-71).
CATALOG description for restrictions for RMAN client connections to a virtual catalog when the RMAN client is from release Oracle Database 10g or earlier.
Typically, you create the recovery catalog in a database created especially for this purpose. Do not create the recovery catalog in a privileged schema such as
The best practice is to create one recovery catalog that serves as the central RMAN repository for many databases. For this reason it is called the base recovery catalog.
The owner of the base recovery catalog can
REVOKE restricted access to the catalog to other database users. Each restricted user has full read/write access to his own metadata, which is called a virtual private catalog. The RMAN metadata is stored in the schema of the virtual private catalog owner. The owner of the base recovery catalog controls what each virtual catalog user can access.
Example 2-70 Creating a Recovery Catalog and Registering a Database
Assume that you start SQL*Plus and connect to the recovery catalog
catdb with administrator privileges. You execute the
CREATE USER statement as follows, replacing password with a user-specified password (see Oracle Database Security Guide for information on creating secure passwords). The SQL statement creates a user
rco in database
catdb and grant the
rco user the
SQL> CREATE USER rco IDENTIFIED BY password 2 DEFAULT TABLESPACE cattbs 3 QUOTA UNLIMITED ON cattbs; SQL> GRANT recovery_catalog_owner TO rco; SQL> EXIT
You then start RMAN and run the following RMAN commands to connect to the recovery catalog database as
rco and create the recovery catalog:
RMAN> CONNECT CATALOG rco@catdb recovery catalog database Password: password connected to recovery catalog database RMAN> CREATE CATALOG;
In the same RMAN session, you connect to a target database using operating system authentication and use the
REGISTER DATABASE command to register this database in the catalog:
RMAN> CONNECT TARGET / RMAN> REGISTER DATABASE; RMAN> EXIT
Example 2-71 Creating a Virtual Private Catalog
Assume that you created the recovery catalog and registered a database as shown in Example 2-70. Now you want to create a virtual private catalog for database user
vpc1. The database version is Oracle Database 12c Release 1 (22.214.171.124). You start SQL*Plus and connect to recovery catalog database
catdb with administrator privileges. You create the
vpc1 user and grant recovery catalog ownership as follows, replacing password with a user-specified password (see Oracle Database Security Guide for information on creating secure passwords):
SQL> CREATE USER vpc1 IDENTIFIED BY password 2 DEFAULT TABLESPACE vpcusers; SQL> GRANT CREATE SESSION TO vpc1; SQL> EXIT
You then start RMAN and connect to the recovery catalog database as the catalog owner
rco. By default, the virtual catalog owner has no access to the base recovery catalog. You use the
GRANT command to grant virtual private catalog access to
vpc1 for RMAN operations on database
prod1 (but not
RMAN> CONNECT CATALOG rco@catdb recovery catalog database Password: password connected to recovery catalog database RMAN> GRANT CATALOG FOR DATABASE prod1 TO vpc1; RMAN> EXIT;
Now the backup operator who will use virtual private catalog
vpc1 is ready to create the virtual catalog. In the following example, the backup operator connects to the recovery catalog database as
vpc1 and registers the database prod1 with
The virtual private catalog is created automatically when catalog privileges are granted to the virtual private catalog owner.
RMAN> CONNECT CATALOG vpc1@catdb recovery catalog database Password: password connected to recovery catalog database RMAN> REGISTER DATABASE prod1; RMAN> EXIT;