Tuesday, 26 November 2013

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

Error:--


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 11/20/2013 05:27:58
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file +DG_ARCH/test/archivelog/2013_11_20/thread_2_seq_199159.7269.832482119
ORA-17503: ksfdopn:2 Failed to open file +DG_ARCH/test/archivelog/2013_11_20/thread_2_seq_199159.7269.832482119
ORA-15012: ASM file '+DG_ARCH/test/archivelog/2013_11_20/thread_2_seq_199159.7269.832482119' does not exist

Cause:
The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log.
This may occur because the archived log was removed by an outside utility without updating the repository.

Fixed
1. Perform a crosscheck, run the following command from within RMAN:
RMAN> change archivelog all crosscheck;
2. Perform a full backup of the database at this point.


No comments:

Post a comment