Resynchronizing the Recovery Catalog
Plug‑in for Oracle automatically runs a full or partial resynchronization of the Recovery Catalog when performing RMAN backups as long the Control File is mounted and the Recovery Catalog database is available at command execution.
You can use the RMAN RESYNC CATALOG command to perform manual Full Resynchronizations when:
You should not need to run RESYNC CATALOG often. For more information, see Using CROSSCHECK to Update the RMAN Repository in the Oracle Database Backup and Recovery Advanced User’s Guide.
To force a Full Resynchronization of the Recovery Catalog, perform the following steps.
Using CROSSCHECK to update the RMAN repository
To ensure that data about backups in the RMAN Repository is synchronized with corresponding data in the NetVault Database, perform a crosscheck. The CROSSCHECK command updates outdated RMAN repository information about backups whose repository records do not match their physical status. For example, if a user removes archive logs from disk with an OS command, the repository still indicates that the logs are on disk, when in fact they are not.
For more information on the CROSSCHECK command, see the Oracle Database Backup and Recovery Basics guide.
Using the RMAN CLI
CLI-based RMAN backups and restores: an overview
If you want use advanced RMAN features that are not supported through Plug‑in for Oracle’s interface, you can perform CLI-based RMAN backups and restores instead of, or with, the plug-in. During CLI-based RMAN backups and restores, the plug-in provides media management functionality for RMAN.
|
IMPORTANT: Before using this functionality, Quest recommends that you thoroughly review the Oracle Database Backup and Recovery Advanced User’s Guide to familiarize yourself with the internals of RMAN. |
Before completing any additional or different steps that are outlined in this topic, review the information provided in the previous topics, such as Installing and removing the plug-in and Configuring the plug-in.