The examples that follow assume
that we have a default installation of an Oracle 11g database; the repository database itself can be
used for other applications if there is no significant performance degradation when RMAN needs
to update metadata in the repository.
CAUTION
Using an RMAN target database for the repository is strongly
discouraged. Loss of the target database prevents any chance of
a successful recovery of the database using RMAN because the
repository metadata is lost along with the target database.
The following sequence of commands creates a tablespace and a user to maintain the metadata
in the repository database. In this and all subsequent examples, a database with a SID of rac, the
RAC database we created in Chapter 10, is used for all repository operations.
424 Oracle Database 11g DBA Handbook
RMAN Command Description
@ Runs an RMAN command script at the pathname specified after the
@. If no path is specified, the path is assumed to be the directory from
which RMAN was invoked.
ADVISE FAILURE Displays repair options for the failure found.
BACKUP Performs an RMAN backup, with or without archived redo logs. Backs
up datafiles, datafile copies, or performs an incremental level 0 or level
1 backup. Backs up an entire database, or a single tablespace or datafile.
Validates the blocks to be backed up with the VALIDATE clause.
CATALOG Adds information about file copies and user-managed backups to the
repository.
Pages:
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662