RESTORE VALIDATE
The restore . . . preview command does not read the actual backupsets, only the catalog information;
if we want to validate whether the backupsets themselves are readable and not corrupted, we use
the restore . . . validate command. As with most other RMAN commands, we can perform the
validation for a datafile, a tablespace, or the entire database. In the following example, we??™ll
perform a validation on the same backupsets that RMAN reported in the previous example for
the USERS tablespace:
RMAN> restore tablespace users validate;
Starting restore at 04-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backup set
channel ORA_DISK_1: reading from backup piece
+RECOV/dw/backupset/2007_09_04/
nnndf0_tag20070904t230656_0.354.632444895
channel ORA_DISK_1: piece
handle=+RECOV/dw/backupset/2007_09_04/
nnndf0_tag20070904t230656_0.354.632444895 tag=TAG20070904T230656
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:02:13
Finished restore at 04-SEP-07
RMAN>
All blocks of the backupsets were read to ensure that they are usable for a restore operation
for the USERS tablespace.
Point in Time Recovery
RMAN can be used to implement point in time recovery, or restoring and recovering a database
up to a timestamp or SCN before the point at which a database failure occurred. As you found
out in Chapter 11, a point in time recovery (PITR) may be useful for recovering from a user error
where a table was dropped yesterday, but the error was not detected until today.
Pages:
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711