ORA-279 signalled during - alter database recover logfile 'xxx'

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".

在RMAN的RECOVER还原过程中，RMAN界面正常，但是检查、刷新告警日志，发现告警日志里面有ORA-279，如下所示：

alter database recover logfile '/u06/archivelog/o1_mf_1_16228_g6oznpbv_.arc'
Thu Feb 21 08:49:48 CST 2019
Media Recovery Log /u06/archivelog/o1_mf_1_16228_g6oznpbv_.arc
Thu Feb 21 08:50:58 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/o1_mf_1_16228_g6oznpbv_.arc'...
Thu Feb 21 08:50:59 CST 2019
alter database recover logfile '/u06/archivelog/o1_mf_1_16229_g6ozp2pv_.arc'
Thu Feb 21 08:50:59 CST 2019
Media Recovery Log /u06/archivelog/o1_mf_1_16229_g6ozp2pv_.arc
Thu Feb 21 08:51:12 CST 2019
ORA-279 signalled during: alter database recover logfile '/u06/archivelog/o1_mf_1_16229_g6ozp2pv_.arc'...

alter database recover cancel
Thu Feb 21 08:52:46 CST 2019
Media Recovery Canceled
Completed: alter database recover cancel


告警日志中ORA-279更像是“**输出消息**”， 而不是“**错误信息**”，它是在提示需要请求的归档日志才能继续恢复。以前在使用RMAN进行RECOVER时没有留意过这个细节信息。顺便记录一下。以免初次遇到这个提示信息的时候，还以为出现了什么异常或错误。<br>

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