Database recovery fails with ORA-00317: file type 0 in header is not log file

PWhile we were performing the clone from RMAN backup, Recovery was failing with the below error

ORA-00279: change 5969245693131 generated at 06/10/2016 23:02:11 needed for

thread 1

ORA-00289: suggestion : /test/arc01/test_1_32850_869208143.arc

ORA-00280: change 5969245693131 for thread 1 is in sequence #32850

ORA-00278: log file '/test/arc01/test_1_32849_869208143.arc' no longer needed

for this recovery

ORA-00317: file type 0 in header is not log file

ORA-00334: archived log: '/test/arc01/test_1_32850_869208143.arc'

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

ORA-01152: file 1 was not restored from a sufficiently old backup

ORA-01110: data file 1: '/test/data01/system01.dbf'

Below were the steps performed to resolve the issue

1 .We have checked the archive log size and did not find any issues with archive log size.

2. After checking the Metalink, We observed that the issue occurs when the archive logs we are trying to apply is corrupted.

3.We have restored the archive log file from backup again and have applied the archive and was able to open the database

 3.a: Apply the archive log

SQL>recover database using backup controlfile until cancel;

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/test/arc01/test_1_32850_869208143.arc

ORA-00279: change 5969245694703 generated at 06/10/2016 23:19:23 needed for

thread 1

ORA-00289: suggestion : /test/arc01/test_1_32851_869208143.arc

ORA-00280: change 5969245694703 for thread 1 is in sequence #32851

ORA-00278: log file '/test/arc01/test_1_32850_869208143.arc' no longer needed

for this recovery

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-00279: change 5969245694711 generated at 06/10/2016 23:19:24 needed for

thread 1

ORA-00289: suggestion : /test/arc01/test_1_32852_869208143.arc

ORA-00280: change 5969245694711 for thread 1 is in sequence #32852

ORA-00278: log file '/test/arc01/test_1_32851_869208143.arc' no longer needed

for this recovery

3.b After archives were successfully applied,Open the database using reset logs option

SQL> alter database open resetlogs;

Database altered.

SQL>

 SQL> select status from v$instance;

STATUS

------------

OPEN