Try adding crosscheck archivelog all; Michael Dinh : XIFIN : 858.436.2929 NOTICE OF CONFIDENTIALITY - This material is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. BE FURTHER ADVISED THAT THIS EMAIL MAY CONTAIN PROTECTED HEALTH INFORMATION (PHI). BY ACCEPTING THIS MESSAGE, YOU ACKNOWLEDGE THE FOREGOING, AND AGREE AS FOLLOWS: YOU AGREE TO NOT DISCLOSE TO ANY THIRD PARTY ANY PHI CONTAINED HEREIN, EXCEPT AS EXPRESSLY PERMITTED AND ONLY TO THE EXTENT NECESSARY TO PERFORM YOUR OBLIGATIONS RELATING TO THE RECEIPT OF THIS MESSAGE. If the reader of this email (and attachments) is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Please notify the sender of the error and delete the e-mail you received. Thank you. From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jay Hostetter Sent: Friday, June 25, 2010 5:55 AM To: oracle-l@xxxxxxxxxxxxx Subject: delete obsolete for archivelogs Oracle Version: 11.1.0.7 OS: Windows 2003 I have a production database that has the retention policy set to REDUNDANCY 2 and the ARCHIVELOG DELETION POLICY BACKED UP 2 TIMES TO DISK. When I issue DELETE NOPROMPT OBSOLETE, the database does NOT delete archivelogs. I have a test database that is identical to the production database. However, the retention policy is set to REDUNDANCY 1. The ARCHIVELOG DELETION POLICY is also set to BACKED UP 2 TIMES TO DISK. When I issue DELETE NOPROMPT OBSOLETE, the database DOES delete archivelogs. We're talking about archivelogs outside of the FRA for both of these databases. In fact, the FRA is not used. What configuration parameter am I missing on production that causes the DELETE NOPROMPT OBSOLETE command to skip the archivelogs? If I delete the archivelogs (with DELETE INPUT or even DELETE NOPROMPT ARCHIVELOG ALL BACKED UP 2 TIMES TO DEVICE TYPE DISK) , I get the annoying RMAN-08138 message for those archivelogs that have not been backed up twice. At this point I'd just be happy suppressing that error message, but I'd really like to know the difference between production and test. Thank you, Jay Here is the rman config for production: RMAN> show all; RMAN configuration parameters for database with db_unique_name SALES2 are: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'H:\Oracle_Backups\SALES2\cf_%F.bck'; CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK; CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE_HOME\PRODUCT\11.1.0\DB_1\DATABASE\SNCFSALES2.ORA'; # default Here is the relevant section of my rman script: # Cleanup the backups based on the retention policy. crosscheck backup; delete noprompt obsolete;