在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.
参考资料：