standby 节点日志报错：

RFS[17]: Assigned to RFS process 12271
RFS[17]: Identified database type as ‘physical standby’: Client is ARCH pid 7737
Fri May 26 12:58:27 2017
RFS[18]: Assigned to RFS process 12273
RFS[18]: Identified database type as ‘physical standby’: Client is ARCH pid 7733
RFS[18]: Opened log for thread 1 sequence 83 dbid 1326947558 branch 937061226
Archived Log entry 101 added for thread 1 sequence 83 rlc 937061226 ID 0x4f24813a dest 2:
Fri May 26 12:58:28 2017
RFS[19]: Assigned to RFS process 12275
RFS[19]: Identified database type as ‘physical standby’: Client is LGWR SYNC pid 7709
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Standby controlfile consistent with primary
RFS[19]: No standby redo logfiles of file size 1073741824 AND block size 512 exist
RFS[19]: No standby redo logfiles selected (reason:7)
Errors in file /u01/app/oracle/diag/rdbms/hbdb2/hbdb2/trace/hbdb2_rfs_12275.trc:
ORA-16086: Redo data cannot be written to the standby redo log
Fri May 26 12:58:29 2017
Media Recovery Log /oradata/standby_log/1_83_937061226.dbf
Media Recovery Waiting for thread 1 sequence 84
Fri May 26 13:04:27 2017
RFS[20]: Assigned to RFS process 12296

trc文件中：
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database does
not contain any viable standby redo logfiles.
ORA-16086: Redo data cannot be written to the standby redo log

是由于没有办法写入standby log导致的。重建standby log 就可以了。