Catalog Maintenance
Earlier in this chapter, we discussed the use of the backup validate command to ensure that all
the files that could be used in a backup operation were available, readable, and not corrupted.
In that example, we found out that we had a mismatch between what the catalog reported and the
archived redo logs on disk; some old archived redo logs were inadvertently removed from disk
during a cleanup operation. In this section, we??™ll step through some of the maintenance operations
we would need to perform to bring the catalog in synch with what actually exists on disk.
RMAN> backup validate database archivelog all;
Starting backup at 05-SEP-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=121 device type=DISK
archived log +RECOV/dw/archivelog/2007_08_27/
thread_1_seq_95.284.631750213 not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 95
. . .
Our first attempt to fix the problem was to remove all obsolete files outside of our recovery
window of four days, keeping an extra day??™s worth of logs, since we have plenty of space in the
flash recovery area.
RMAN> delete obsolete recovery window of 5 days;
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log 131 25-AUG-07
/u01/app/oracle/product/11.
Pages:
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716