Re: RMAN - Removing 'non-existant' archived logs

From: Robert Freeman <>
Date: Mon, 17 Aug 2009 21:22:36 -0700 (PDT)
Message-ID: <>

When you run the crosscheck command the backup file will take on a status of expired. This will continue forever until you then run the delete expired command. This will mark expired backup sets as deleted. Then they won't show up in the crosscheck command again. This means that if the files show up again, RMAN will not pick them up when you run a crosscheck command. You will have to catalog those files.

All this is covered in my RMAN book.



 Robert G. Freeman
Oracle ACE
Oracle Database 11g RMAN Backup and Recovery (Oracle Press) - ON IT'S WAY SOON! OCP: Oracle Database 11g Administrator Certified Professional Study Guide (Sybex) Oracle Database 11g New Features (Oracle Press) Portable DBA: Oracle (Oracle Press)
Oracle Database 10g New Features (Oracle Press) Oracle9i RMAN Backup and Recovery (Oracle Press) Oracle9i New Features (Oracle Press)
Other various titles out of print now... Blog: The LDS Church is looking for DBA's. You do have to be a Church member in good standing. A lot of kind people write me, concerned I may be breaking the law by saying you have to be a Church member. It's legal I promise! :-)

  • Original Message ---- From: Steve Baldwin <> To: oracle_l <> Sent: Monday, August 17, 2009 6:30:37 PM Subject: RMAN - Removing 'non-existant' archived logs

(Version 11.1)

I'm just in the process of setting up rman for a machine.

Somehow I have a situation where when I do a "crosscheck archivelog all" I get told about a whole bunch of failures for non-existant log files - e.g.

validation failed for archived log
archived log file name=/database1/oracle-archive/arch.0676670550.0001.0000000503.dbf RECID=678 STAMP=692965495

What do I do to clean up these messages without deleting genuine log files?



This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email.

-- Received on Mon Aug 17 2009 - 23:22:36 CDT

Original text of this message