使用rman执行recover database 的时候出现RMAN-06054的错误提示

最新推荐文章于 2024-09-19 18:09:24 发布

转载最新推荐文章于 2024-09-19 18:09:24 发布 · 525 阅读

本文介绍了一种在使用RMAN进行数据库恢复过程中遇到RMAN-06054错误的情况及解决方案。当恢复所需日志在控制文件或恢复目录中未找到时，若日志仍可用，则需通过CATALOG命令添加；若已丢失，则需进行不完全恢复，并使用ALTER DATABASE OPEN RESETLOGS命令打开数据库。

RMAN> recover database;

Starting recover at 14-FEB-17
using channel ORA_DISK_1

starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=4120
channel ORA_DISK_1: reading from backup piece /dbbackup/hcms/backupset/2/FULL_HCMS_LOG_20170214_e4rsibf3_1_1.rmanbak
channel ORA_DISK_1: piece handle=/dbbackup/hcms/backupset/2/FULL_HCMS_LOG_20170214_e4rsibf3_1_1.rmanbak tag=TAG20170214T125603
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/app/oracle/archive/1_4120_858952281.dbf thread=1 sequence=4120
unable to find archived log
archived log thread=1 sequence=4121
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/14/2017 13:44:51
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 4121 and starting SCN of 152305555

在11g官方文档error messages中对错误描述如下：
RMAN-06054: media recovery requesting unknown archived log for thread string with sequence string and starting SCN of string

Cause: Media recovery is requesting a log whose existence is not recorded in the recovery catalog or target database control file.

Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point-in-time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command.

可见，出先此错误的原因是恢复需要的日志记录在控制文件或恢复目录中找不到。解决方法分两种情况：
1.如果相关的日志存在且可用的话，就将此日志记录添加到控制文件或恢复目录中。
2.如果相关的日志已经被删除了或不可用了，那么就按照错误的提示scn将数据库恢复到此scn，本案例是152305555。也就是说此时数据库只能进行不完全恢复了.
3.在打开数据库时得使用resetlogs打开。

RMAN> recover database until scn 152305555;

Starting recover at 14-FEB-17
using channel ORA_DISK_1

starting media recovery
media recovery complete, elapsed time: 00:00:01

Finished recover at 14-FEB-17

RMAN> alter database open resetlogs;

database opened

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/12798004/viewspace-2133511/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/12798004/viewspace-2133511/