轉自：http://blog.itpub.net/29800581/viewspace-1307267/
使用rman執行recover database 的時候出現RMAN-06054的錯誤提示： RMAN> recover database; Starting recover at 21-OCT-14 using channel ORA_DISK_1 starting media recovery archived log for thread 1 with sequence 1 is already on disk as file /u01/app/archivelog/dest2/1_1_861389770.dbf archived log for thread 1 with sequence 2 is already on disk as file /u01/app/archivelog/dest1/1_2_861389770.dbf archived log for thread 1 with sequence 3 is already on disk as file /u01/app/archivelog/dest1/1_3_861389770.dbf archived log for thread 1 with sequence 4 is already on disk as file /u01/app/archivelog/dest1/1_4_861389770.dbf archived log for thread 1 with sequence 5 is already on disk as file /u01/app/archivelog2/dest1/1_5_861389770.dbf archived log for thread 1 with sequence 6 is already on disk as file /u01/app/archivelog2/dest1/1_6_861389770.dbf archived log file name=/u01/app/archivelog/dest2/1_1_861389770.dbf thread=1 sequence=1 archived log file name=/u01/app/archivelog/dest1/1_2_861389770.dbf thread=1 sequence=2 archived log file name=/u01/app/archivelog/dest1/1_3_861389770.dbf thread=1 sequence=3 archived log file name=/u01/app/archivelog/dest1/1_4_861389770.dbf thread=1 sequence=4 archived log file name=/u01/app/archivelog2/dest1/1_5_861389770.dbf thread=1 sequence=5 archived log file name=/u01/app/archivelog2/dest1/1_6_861389770.dbf thread=1 sequence=6 unable to find archived log archived log thread=1 sequence=7 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 10/21/2014 01:28:11 RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 7 and starting SCN of 2292709 在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，本案例是2292709。也就是說此時數據庫只能進行不完全恢復了，在打開數據庫時得使用resetlogs打開。 RMAN> recover database until scn 2292709; Starting recover at 21-OCT-14 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:00 Finished recover at 21-OCT-14