Dave Brown wrote, in part,  on 11/15/2006 1:20 PM:
> Log disk filled up
>
> Oracle/dba guy deleted files to make room
>
> Job fails with new error stating the log file it is supposed to backup
> does not exist.
>   

As other folks have suggested, step 2 was *bad* and "crosscheck".  There 
are various versions of crosscheck.  Perhaps

    RMAN> change archivelog all validate;
    RMAN> change archivelog all crosscheck;

is what you're looking for to get by your DBA making a mistake?

There are alternatives, however, to deleting archive redologs!

Although your "normal" script may not function because it will try to 
flush data out to archive redologs .... and there is no space for it in 
our case ..., a good trick is to have a minimalist script,  to just back 
up and delete the archive redologs (or you can just type the commands to 
RMAN).   Once space is cleared via backup, production continues and your 
more normal backup script may be used.  My "minimalist script" prompts 
for a "FROM" value so that I can get by someone stupidly deleting 
files.  :-)

In any event and asap, after getting going, take a full backup of your 
DB, because with the erased files, Oracle will not have enough 
information to restore past the start of the missing archive redologs.

There are other methods to get out of full-disk situations, but this one 
is relatively quick, reliable and maintains all information ... and has 
worked for me a number of times.

Hope this helps, even though it doesn't necessarily answer what was 
asked ;-)

cheers, wayne