Database Reference
In-Depth Information
disk space available. You can then have RMAN move the newly cataloged backup files to
tape again (assuming you have the time and network bandwidth).
Another option is if all the files are in the FRA, then you can use the RMAN CATALOG
RECOVERY AREA command to re-catalog all files that are contained in the database's FRA.
Another occasion when you will need to use the CATALOG command is if backups were
inadvertently deleted from the recovery catalog by the DBA, some wayward script, or an
incorrectly set retention criteria. In this case, the backup set pieces might still be available
but they will be shown as deleted in the database and in the recovery catalog. In this case,
you can simply re-catalog these backups to have them added back to the database and the
recovery catalog.
As you can see, the RMAN CATALOG command is a very powerful command and very
helpful to have around when you have lost a backup record either in the control file or in
the recovery catalog.
Using the RMAN Virtual Private Catalog
You might have noticed that the catalog-schema owner has access to all data in the recovery
catalog. In many enterprises there may be hundreds of databases and dozens of people who
have administrative access to databases. In these cases, you want to be able to restrict access
to database backup records in the recovery catalog to those people who are authorized to
have access to those records. In previous versions of the RMAN recovery catalog, this kind
of separation would require different recovery catalogs to be created.
Oracle Database 11 g introduced the notion of the RMAN virtual private catalog.
The Oracle virtual private catalog provides the ability to secure the records in the
RMAN recovery catalog on a user-by-user basis. Thus, one user may be able to see all
records in the recovery catalog and another user may be able to see only records of a
subset of the databases in the catalog.
In the following sections, we will discuss how to create a virtual catalog and how to grant
users access to databases contained within it. We will discuss how to create the RMAN virtual
private catalog first, and then we will discuss administration of the virtual private catalog.
Creating the RMAN Virtual Private Catalog
If you want to use the RMAN virtual private catalog (RVPC) , you start with a regular
recovery catalog. The recovery catalog schema should have been created and the databases
registered (you can, of course, register databases later), and it can be brand new or already
in use.
Now that you have a recovery catalog, let's assume you have registered two databases
in the recovery catalog; one is called ORCL and one is called secret . Let's assume you have
a DBA named Ed who you don't quite trust (he's a seedy-looking guy with tattoos of the
Smurfs all over his arms). Because you don't trust him, you want him to be able to access
only the ORCL database RMAN records. The secret database records will remain a mystery
Search WWH ::




Custom Search