RMAN-06054 report duri…

Symptoms:

RMAN恢复时出现

 

 RMAN-06054: media recovery requestingunknown archived log for thread 1 with sequence 22488 and startingSCN of 10242830716955

 

RMAN> recover database;

Starting recover at 02-OCT-14
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting incremental datafile backup setrestore
channel ORA_DISK_1: specifying datafile(s) to restore from backupset
destination for restore of datafile 00214:/pool08/test3/db/apps_st/data/PROD/datafile/o1_mf_apps_ts__b2bycn8v_.dbf
channel ORA_DISK_1: reading from backup piece/backup_01/backupset/lv1_18243_20140925
channel ORA_DISK_1: piecehandle=/backup_01/backupset/lv1_18243_20140925 tag=LV1
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time:00:42:56

starting media recovery

unable to find archived log
archived log thread=1 sequence=22488
RMAN-00571:===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS===============
RMAN-00571:===========================================================
RMAN-03002: failure of recover command at 10/02/2014 22:17:01
RMAN-06054: media recovery requesting unknown archived log forthread 1 with sequence 22488 and starting SCN of10242830716955

 

Cause:

 

没有SETUNTIL，rman尝试完全恢复，由于重做日志不存在，Oracle不知道应用到哪个归档日志为止，会请求一个不存在的归档日志文件进行恢复（其实应该是当前的重做日志文件)

 

 

参考如下文档：

 

 

 

RMAN-6054 report during recover database (文档 ID880536.1)

---

In thisDocument

SymptomsCauseSolution

---

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4[Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 22-Apr-2013***

Symptoms

RMAN-6054 error is reported during recover database to anotherbox with the following rman script

3> run {
...
12> restore database;
13> recover database;
...
18> }

 

RMAN-06054: media recovery requesting unknown log: threadstring seq string lowscn string

 

Comment: the set until ... clause is not included in the script andthe redo log does not exist in the new box.

Cause

As the "set until ..." clause is not included , complete recoveris performed. During complete recover , the oracle will try toapply all the archivelog based on the restored datafiles, then try to apply the change in the redolog files , ifthe redo logfiles does not exist, oracle will beunaware which one is the last archivelog need to apply and where tostart apply the change in the redo log files. The rman-06054 willbe reported after the lastest archivelog was applied, because theoracle will try to request a nonexist archivelog (which should bethe current redolog file).

Solution

Specify a recover end point using the "set until" clause.

run {
...
set until sequence = ;  -- specify therecover end point.
restore database;
recover database;
....
}