I suspect that you are right in that it's a MML layer issue then.... I've seen this when the backup storage device removes backup set pieces and RMAN still thinks they are there because the retention criteria is not synchronized. RF Robert G. Freeman Oracle Press Author Principle Engineer/Team Manager The Church of Jesus Christ of Latter-Day Saints Collaborate '07 Come join my APEX University Session and Join me to talk about Evolutionary Database Development!! The LDS Church is Hiring DBAs! Contact me if you are interested! -----Original Message----- From: Jared Still [mailto:jkstill@xxxxxxxxx] Sent: Tuesday, March 20, 2007 7:30 PM To: Robert Freeman Cc: fuadar@xxxxxxxxx; Allen, Brandon; Oracle-L Freelists Subject: Re: RMAN recovery from tape with automatic channels On 3/20/07, Robert Freeman <robertgfreeman@xxxxxxxxx> wrote: This is a restore you are trying to do, not a backup.... So Fuad's example doesn't quite work. Ah, I didn't fully read his example and assumed he was trying a restore. Backups are not a problem. It would appear that the RMAN control file or the recovery catalog thinks that the backup you need to restore is sitting on disk somewhere and not tape. .... do the following command: list backup of database summary; Is the device type DISK?? If it is, thats why it's trying to goto disk to get those backupset pieces. How did these get moved to tape? Manually or via RMAN? I can run that command in the morning. However, these backups were all made directly to tape via RMAN. -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist