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

RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
Cause: The archived log was not found. The recovery catalog or target database control file 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 recovery catalog or target database control file.
Action: If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the recovery catalog or target database control file by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable.

0 条评论
分类：大数据

默认排序时间排序

1 个回答

小智 2018-08-30 19:06

RMAN-06059：未找到预期的归档日志，归档日志的丢失会损害可恢复性,
.原因：找不到归档日志。恢复目录或目标数据库控制文件认为它确实存在。如果归档日志实际上已丢失，并且没有备份，则数据库不能在归档日志覆盖的时间点内恢复。这可能会发生，因为归档日志被外部实用程序删除，而不更新恢复目录或目标数据库控制文件。,
.操作：如果已使用外部实用程序删除归档日志，并且归档日志已备份，则可以通过运行CROSSCHECK ARCHIVELOG ALL来同步恢复目录或目标数据库控制文件。如果先前未备份归档日志，则应对数据库和归档日志进行完全备份，以保持可恢复性。以前的备份不能完全恢复。,
.

aiaiDBA

13718043309

010-86462881

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

1 个回答

相似问题