258.630244583
4 Full 2741782 29-AUG-07
+DATA/dw/datafile/users.259.630244583
5 Full 2741782 29-AUG-07
+DATA/dw/datafile/example.265.630244801
6 Full 2741782 29-AUG-07
+DATA/dw/datafile/users_crypt.267.630456963
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
230 Full 80.00K DISK 00:00:12 29-AUG-07
BP Key: 232 Status: AVAILABLE Compressed: NO Tag:
TAG20070829T181238
Piece Name: +RECOV/dw/backupset/2007_08_29/
nnsnf0_tag20070829t181238_0.293.631908931
SPFILE Included: Modification time: 28-AUG-07
SPFILE db_unique_name: DW
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
244 Full 9.48M DISK 00:00:11 29-AUG-07
BP Key: 246 Status: AVAILABLE Compressed: NO Tag:
TAG20070829T181535
Piece Name:
+RECOV/dw/autobackup/2007_08_29/
s_631908935.294.631908947
SPFILE Included: Modification time: 28-AUG-07
Chapter 12: Using Recovery Manager (RMAN) 439
SPFILE db_unique_name: DW
Control File Included: Ckp SCN: 2741907 Ckp time: 29-AUG-07
RMAN>
One of the full backups can be used in conjunction with the archived redo logs (stored
by default in the flash recovery area residing in the ASM disk group +RECOV) to recover the
database to any point in time up to the last committed transaction.
Figure 12-5 shows a whole database backup configured to run using OEM. Notice that you
can view, copy, or edit the RMAN script that OEM generates.
Pages:
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681