. .
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00002 name=+DATA/dw/datafile/sysaux.257.630244581
input datafile file number=00001 name=+DATA/dw/datafile/system.256.630244579
input datafile file number=00006
name=+DATA/dw/datafile/users_crypt.267.630456963
input datafile file number=00005
name=+DATA/dw/datafile/example.265.630244801
input datafile file number=00007
name=+DATA/dw/datafile/inet_star.268.632004213
input datafile file number=00003
name=+DATA/dw/datafile/undotbs1.258.630244583
input datafile file number=00008
name=+DATA/dw/datafile/inet_intl_star.269.632009933
input datafile file number=00004 name=+DATA/dw/datafile/users.259.630244583
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:05
. . .
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
List of Control File and SPFILE
===============================
File Type Status Blocks Failing Blocks Examined
------------ ------ -------------- ---------------
SPFILE OK 0 2
Control File OK 0 602
Finished backup at 04-SEP-07
RMAN>
Chapter 12: Using Recovery Manager (RMAN) 455
No errors were found during the validation; RMAN read every block of every archived redo
log file and datafile to ensure that they were readable and had no corrupted blocks. However, no
backups were actually written to a disk or tape channel.
Recovery Operations
Every good backup plan includes a disaster recovery plan so that we can retrieve the datafiles and
logs from the backups and recover the database files.
Pages:
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699