RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
RMAN backup run encountered “RMAN-06059: expected archived log not found, loss of archived log compromises recoverability”
Solution for the mentioned error is to Crosscheck your archive logs from RMAN prompt and delete those expired logs which are not needed anymore.
While crosscheck archivelogs, RMAN will mark archive log as expired in its repository (i.e. controlfile or catalog) those not physically present in server so we can go ahead delete expired archives from controlfile or catalog repository.
Error log:
MAN> 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.
## Physically not available archive logs are marked as expired which are not required for recovery.
RMAN> CROSSCHECK ARCHIVELOG ALL;
##delete all archive logs which are marked as expired while crosscheck.
RMAN> DELETE EXPIRED ARCHIVELOG ALL;
RMAN backup run encountered “RMAN-06059: expected archived log not found, loss of archived log compromises recoverability”
Solution for the mentioned error is to Crosscheck your archive logs from RMAN prompt and delete those expired logs which are not needed anymore.
While crosscheck archivelogs, RMAN will mark archive log as expired in its repository (i.e. controlfile or catalog) those not physically present in server so we can go ahead delete expired archives from controlfile or catalog repository.
Error log:
MAN> 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.
## Physically not available archive logs are marked as expired which are not required for recovery.
RMAN> CROSSCHECK ARCHIVELOG ALL;
##delete all archive logs which are marked as expired while crosscheck.
RMAN> DELETE EXPIRED ARCHIVELOG ALL;
No comments:
Post a Comment