We will review each of these briefly in this section.
Many features of RMAN do not have equivalents in the backup methods presented in Chapter 11.
We??™ll contrast the advantages and disadvantages of using RMAN versus the more traditional
methods of backups.
I
Chapter 12: Using Recovery Manager (RMAN) 419
RMAN Components
The first, and minimal, component in the RMAN environment is the RMAN executable. It is available
along with the other Oracle utilities in the directory $ORACLE_HOME/bin, and it??™s installed by
default with both the Standard and Enterprise Editions of Oracle 11g. From a command-line prompt,
you can invoke RMAN with or without command-line arguments; in the following example, we??™re
starting up RMAN using operating system authentication without connecting to a recovery catalog:
[oracle@dw ~]$ rman target /
RMAN>
The command-line arguments are optional; we can specify our target database and a recovery
catalog from the RMAN> prompt also. In Figure 12-1, you can see how to access RMAN features
from Oracle Enterprise Manager.
RMAN would not be of much use unless we have a database to back up. One or more target
databases can be cataloged in the recovery catalog; in addition, the control file of the database
being backed up contains information about backups performed by RMAN. From within the
RMAN client, you can also issue SQL commands for those operations you cannot perform with
native RMAN commands.
Pages:
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653