Once the tablespace is back online, it is available for use again, without the loss of any committed
transactions to tables in the tablespace.
Chapter 12: Using Recovery Manager (RMAN) 459
Restoring a Datafile
Restoring a datafile is a very similar operation to restoring a tablespace. Once the missing or
corrupted datafile is identified using the V$DATAFILE_HEADER view, the RMAN commands are
very similar to the previous example; the tablespace is taken offline, the datafile(s) are restored
and recovered, and the tablespace is brought back online. If only file number 7 was lost, the
recover and restore commands are as simple as this:
RMAN> restore datafile 7;
RMAN> recover datafile 7;
Using OEM, the procedure is also very straightforward. In Figure 12-14, we configure the
datafile restore by selecting the missing datafile (#7) in the INET_STAR tablespace.
In Figure 12-15, we have the option to restore the datafile to an alternate location; in this
case, we want to restore it to the original location. If the failed disk drive containing the datafile
could not be repaired, we would specify an alternate location for the datafile.
Before the RMAN job is submitted, we have one more chance to review the configuration of
the job in Figure 12-16. Figure 12-17 shows the actual RMAN commands that will be run to perform
the requested operation.
FIGURE 12-14 Selecting the datafile to restore
460 Oracle Database 11g DBA Handbook
FIGURE 12-15 Specifying a location for the restored datafile
FIGURE 12-16 Review the restore options
Chapter 12: Using Recovery Manager (RMAN) 461
Restoring an Entire Database
Although the loss of an entire database is a serious and disastrous event, having a solid backup
and recovery policy, as we??™ve described previously in this chapter, can bring the database back
up to the most recent committed transaction with a minimum of effort.
Pages:
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705