This module discussed the last few maintenance activities that you should know before you start backing up your database.
Now that you have completed this module, you should be able to:
- Add information to the recovery catalog
- Re-create your recovery catalog
- Use the
- Use the
- Create and use stored scripts
- Use the
Use the Oracle-supplied data dictionary views . We have purposely not spent much time on the complete syntax for stored scripts. This will be covered in greater detail as you write scripts for your backup operations. The
list commands will become your primary method to monitor your recovery catalog.
You will learn the complete syntax for stored scripts as you begin to write scripts for your backup operations. The best source for information on stored scripts is in the Oracle8 documentation and samples from your peers.
In the next module, you will learn about making backup sets and image copies with RMAN.
If the recovery catalog database is lost or damaged, and recovery of the recovery catalog database through the normal Oracle recovery mechanisms is not possible, then you must re-create the catalog.
You have two options for partially re-creating the contents of the old catalog:
- Issue catalog commands to re-catalog archived redo logs, backup control files, and datafile copies.
- Use the resync catalog from controlfilecopy command to extract information from a backup control file and rebuild the recovery catalog from it.
You can re-create information about backup sets only by using the resync catalog from controlfilecopy command, because the catalog command does not support re-cataloging of backup pieces or backup sets. RMAN does not verify that the files being re-cataloged still exist, so the resynchronization may add records for files that no longer exist. Remove such records by issuing
change ... crosscheck
or crosscheck backup commands.