RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
Published 2 years ago by Jignesh Jethwa
Oracle 11g Logo
While RMAN full backup, today i have encountered “RMAN-06059: expected archived log not found, loss of archived log compromises recoverability”
RMAN error.
Solution for the mentioned error is to Crosscheck your archive logs from RMAN prompt and delete those expired logs who are not needed anymore.
While crosscheck archivelogs, RMAN will marked archives as Expired in his repository (i.e. controlfile or catalog) those who are not physically present there. So we can easily delete expired archives from controlfile or catalog repository.
Error log:
RMAN> RUN
2> {
3> ALLOCATE CHANNEL backup1 DEVICE TYPE DISK FORMAT 'Z:\RMAN\%U';
4> BACKUP DATABASE PLUS ARCHIVELOG;
5> }
using target database control file instead of recovery catalog
allocated channel: backup1
channel backup1: SID=70 device type=DISK
Starting backup at 10-SEP-14
current log archived
released channel: backup1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 09/10/2014 18:22:35
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file E:\ORACLE\--ORACLE_SID--\ORAARCH\1_35338_778192583.DBF
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
SOlution
RMAN> CROSSCHECK ARCHIVELOG ALL;
Above command will give information of expired RMAN repository after verification. (i.e. in catalog or controlfile)
Above will marked archives as Expired who are not available physically and who are not required for any kind of recovery..
RMAN> DELETE EXPIRED ARCHIVELOG ALL;
Above command will delete all archive logs who are marked as expired while crosscheck.
This comment has been removed by a blog administrator.
ReplyDelete