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

Answer Posted / guest

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.

Action: If the archived log has been removed with an outside
utility and the archivelog has already been backed up, then
you can synchronize the repository by running CROSSCHECK
ARCHIVELOG ALL. If the archivelog has not been previously
backed up, then you should take a full backup of the
database and archivelogs to preserve recoverability.
Previous backups are not fully recoverable.

Please add more information about this Error

Is This Answer Correct ?    1 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

RMAN-05017: no copy of datafile number found to recover

1887


NZE-28890: Entrust Login Failed

1409


IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

2620


When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............

2323


ORA-26028: index string.string initially in unusable state

3403






In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2329


ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2317


ORA-26027: unique index string.string partition string initially in unusable state

6161


IMG-02003: 2FF03 - incorrect color histogram feature specification

1203


IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2301


ORA-26030: index string.string had string partitions made unusable due to:

1562


IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1239


ORA-16516: The current state is invalid for the attempted operation.

8070


NZE-28868: Peer certificate chain check failed.

2265


ORA-16627: No standby databases support the overall protection mode.

3560