In the following scenario,
we have lost all datafiles. However, because we have multiplexed the control file and online redo
log files on many different disks, we will have them available during the RMAN restore and recovery
operation. Alternatively, you can restore the control files or copy the online redo log files to the
other destinations before mounting the database. If this is not feasible because the alternate disk
locations are not available, you can alter your parameter file or SPFILE to indicate which files are
still available.
The entire restore and recovery operation can be performed within RMAN; first, we start up
RMAN and open the database in mount mode, just as if we used the startup mount command at
a SQL*Plus prompt:
[oracle@oltp oracle]$ rman target / catalog rman/rman@rac
Recovery Manager: Release 11.1.0.6.0 -
Production on Tue Sep 4 22:36:05 2007
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)
FIGURE 12-17 RMAN commands for the restore options
462 Oracle Database 11g DBA Handbook
recovery catalog database Password:
connected to recovery catalog database
RMAN> startup mount
Oracle instance started
database mounted
Total System Global Area 422670336 bytes
Fixed Size 1300352 bytes
Variable Size 360712320 bytes
Database Buffers 54525952 bytes
Redo Buffers 6131712 bytes
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN connects to the database and identifies it as being unavailable; this is the same as
connecting to SQL*Plus and seeing the message ???Connected to an idle instance.
Pages:
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706