ctl';
After restoring the control files, you must perform complete media recovery of your database
and open the database with the resetlogs option. Complete media recovery can be performed
using RMAN or the methods described in Chapter 11.
Restoring a Tablespace
If the disk containing the datafiles for a tablespace fails or becomes corrupted, recovery of the
tablespace is possible while the database remains open and available. The exception to this is the
SYSTEM tablespace. In our dw database, suppose the disk containing the datafiles for the USERS
tablespace has crashed. After the first phone call from the users (which happened even before
OEM notified us of the error), we can check the dynamic performance view V$DATAFILE_HEADER
to see which datafiles need recovery:
SQL> select file#, status, error, tablespace_name, name
2 from v$datafile_header;
FILE# STATUS ERROR TABLESPACE_NAME NAME
------- ------- ----------- --------------- -------------------------
1 ONLINE SYSTEM +DATA/dw/datafile/system.
256.630244579
2 ONLINE SYSAUX +DATA/dw/datafile/sysaux.
257.630244581
3 ONLINE UNDOTBS1 +DATA/dw/datafile/undotbs
1.258.630244583
4 ONLINE FILE NOT
FOUND
5 ONLINE EXAMPLE +DATA/dw/datafile/example
Chapter 12: Using Recovery Manager (RMAN) 457
.265.630244801
6 ONLINE USERS_CRYPT +DATA/dw/datafile/users_c
rypt.267.630456963
7 ONLINE INET_STAR +DATA/dw/datafile/inet_st
ar.268.632004213
8 ONLINE INET_INTL_STAR +DATA/dw/datafile/inet_in
tl_star.
Pages:
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702