284.631750213 RECID=38 STAMP=631750217
validation succeeded for archived log
archived log file
name=/u01/app/oracle/product/11.1.0/db_1/dbs/arch1_114_630244724.dbf RECID=75 STAMP=632020373
. . .
archived log file name=/u01/app/oracle/product/11.1.0/db_1/dbs/arch1_147_630244724.dbf
RECID=141 STAMP=632444769
validation succeeded for archived log
archived log file
name=+RECOV/dw/archivelog/2007_09_04/thread_1_seq_147.353.632444769
RECID=142 STAMP=632444769
Crosschecked 69 objects
RMAN>
The missing archived redo logs are now marked as EXPIRED in the catalog, and they won??™t be
considered when validating backups or for performing restore or recovery operations.
All datafiles that RMAN could consider for a backup operation, including archived redo logs,
are available and readable.
REPORT and LIST
All throughout this chapter, I??™ve provided a number of examples of how to extract information
from the recovery catalog, whether it resides in the target database control file or in a catalog
database repository. We??™ve used both the list and report commands. The primary difference
Chapter 12: Using Recovery Manager (RMAN) 473
between these commands is in their complexity: The list command displays information about
backupsets and image copies in the repository as well as lists the contents of scripts stored in the
repository catalog:
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
487 B 0 A DISK 30-AUG-07 1 1 YES
TAG20070830T222903
509 B F A DISK 30-AUG-07 1 1 NO
TAG20070830T223054
624 B F A DISK 03-SEP-07 1 1 NO
TAG20070903T133622
661 B F A DISK 03-SEP-07 1 1 YES
TAG20070903T224442
677 B F A DISK 03-SEP-07 1 1 NO
TAG20070903T224753
744 B F A DISK 04-SEP-07 1 1 YES
TAG20070904T215119
768 B F A DISK 04-SEP-07 1 1 NO
TAG20070904T215311
889 B F A DISK 04-SEP-07 1 1 YES
TAG20070904T230656
915 B F A DISK 04-SEP-07 1 1 NO
TAG20070904T230932
RMAN>
In contrast, the report command performs a more detailed analysis of the information in the
recovery catalog; as in one of our previous examples, we used report to identify which database
files needed backups to comply with our retention policy.
Pages:
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718