RMAN-06059: expected archived log not found, lost of
archived log compromises recoverability
Answer / 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 |
ORA-04047: object specified is incompatible with the flag specified
ORA-29906: indextype string.string does not exist
ORA-19699: cannot make copies with compression enabled
NZE-29161: software integrity self-test failure
IMP-00004: invalid username or password
ORA-23423: job number string is not positive
DRG-52113: improper Japanese string string of length number
TNS-01097: TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
UDE-00005: unexpected End-Of-File encountered while reading input
QSM-01061: illegal query expression
ORA-31062: Cannot delete an unsaved resource
TNS-01009: service [<listener_name>] : get the service information of the listener