在RMAN的RECOVER還原過程中，RMAN界面正常，但是檢查、刷新告警日誌，發現告警日誌裡面有ORA-279，如下所示： alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.arc'... ...
在RMAN的RECOVER還原過程中，RMAN界面正常，但是檢查、刷新告警日誌，發現告警日誌裡面有ORA-279，如下所示：
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.arc'Thu Feb 21 08:49:48 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.arc
Thu Feb 21 08:50:58 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.arc'...Thu Feb 21 08:50:59 CST 2019
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16229_g6ozp2pv_.arc'Thu Feb 21 08:50:59 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16229_g6ozp2pv_.arc
Thu Feb 21 08:51:12 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16229_g6ozp2pv_.arc'...Thu Feb 21 08:51:12 CST 2019
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16230_g6ozrswb_.arc'Thu Feb 21 08:51:12 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16230_g6ozrswb_.arc
Thu Feb 21 08:51:39 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16230_g6ozrswb_.arc'...Thu Feb 21 08:51:39 CST 2019
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16231_g6ozsj8q_.arc'Thu Feb 21 08:51:39 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16231_g6ozsj8q_.arc
Thu Feb 21 08:51:54 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16231_g6ozsj8q_.arc'...Thu Feb 21 08:51:54 CST 2019
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16232_g6ozt53s_.arc'Thu Feb 21 08:51:54 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16232_g6ozt53s_.arc
Thu Feb 21 08:52:13 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16232_g6ozt53s_.arc'...Thu Feb 21 08:52:13 CST 2019
alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16233_g6p6ojcz_.arc'Thu Feb 21 08:52:13 CST 2019
Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16233_g6p6ojcz_.arc
Thu Feb 21 08:52:46 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16233_g6p6ojcz_.arc'...Thu Feb 21 08:52:46 CST 2019
alter database recover cancel
Thu Feb 21 08:52:46 CST 2019
Media Recovery Canceled
Completed: alter database recover cancel
其實這個場景下，告警日誌中ORA-279更像是“輸出消息”， 而不是“錯誤信息”，它是在提示需要請求的歸檔日誌才能繼續恢復。以前在使用RMAN進行RECOVER時沒有留意過這個細節信息。順便記錄一下。以免初次遇到這個提示信息的時候，還以為出現了什麼異常或錯誤。
[root@DB-Server 2019_02_16]$ oerr ora 279
00279, 00000, "change %s generated at %s needed for thread %s"
// *Cause: The requested log is required to proceed with recovery.
// *Action: Please supply the requested log with "ALTER DATABASE RECOVER
// LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE
// RECOVER CANCEL".
Yes, you can ignore the ORA-279s. Treat them as "messages" rather then "errors".
You need to ensure that all archivelogs are being applied by the recovery process.
參考資料：
https://community.oracle.com/thread/638113
