ORA-19625: error identifying file

Archive Sweep got failed :

Found many archive backups got failed during the timeStamp [arch_09012010_18 hours*( 6.00pm PST) - 18:30(6.20pm PST)]
and results in the following error

RMAN-03002: failure of backup command at 01/09/2010 18:22:41
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/oracle/xxxxxx/10.2.0/dbs/arch/1_7631_677955387.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3

Cause :
Recovery Catalog Database : rcvcat
Target Database Name : xxxxxx

Here two backups for the database (xxxxxx) got kicked automatically.
first one started at 18:16:46sec and the second archive backup started at 18:16:49sec.
Archive backup which ran first, successfully archived the following file 1_7631_677955387.dbf and
in a fraction of second the second archive backup tried to backup the same file,
which leads to this error.
ORA-19625: error identifying file /u01/oracle/ascpconv/db/tech_st/10.2.0/dbs/arch/1_7631_677955387.dbf
ORA-27037: unable to obtain file status.
(this is the same file backed up and deleted by the first running archive backup(started at 46sec)).

Its Purely, crontab timing problem.

History :

oracle@
rcvcat:/opt/oracle/rcvcat/10.2.0/admin/rcvcat/log/xxxxxx> ls -ltr arch_09012010_18*
-rw-r----- 1 oracle oinstall 2204 Jan 9 18:22 arch_09012010_18:16:49.log
-rw-r----- 1 oracle oinstall 2542 Jan 9 18:24 arch_09012010_18:16:46.log

OUTPUT OF arch_09012010_18:16:46.log :

archive log filename=/u01/oracle/xxxxx/db/10.2.0/dbs/arch/1_7631_677955387.dbf recid=8604 stamp=707854752
Finished backup at 09:01:2010 18:21:33

OUTPUT OF arch_09012010_18:16:49.log :

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/oracle/xxxxxx/dbs/10.2.0/dbs/arch/1_7631_677955387.dbf
ORA-27037: unable to obtain file status

Impact :

No impact on database as the archivelog file is already backed up successfully.