Alert log shows no standby redo logfiles tips

Question:  I'm getting this message in my alert log:

Primary database is in MAXIMUM PERFORMANCE mode
No standby redo logfiles of size 204800 blocks available
Fri Feb 12 15:08:31 2015
Primary database is in MAXIMUM PERFORMANCE mode
No standby redo logfiles of size 204800 blocks available

Answer:  This is a "noise" alert log message that can sometimes be removed by ensuring that your redo log groups on primary and standby are absolutely identical.  There are also reports that adding additional archiver processes (via increasing the value of the log_archive_max_processes parameter). 

See MOSC note 405836.1 for details and see these important notes on LNS log transport waits.

The Oracle Streams documentation notes some possible reasons for this alert log message:

If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database.  At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database:

The primary database will shut down if it is operating in maximum protection mode, or the primary database will change to maximum performance mode if it is operating in maximum availability mode.  The RFS process on the standby database will create an archived redo log file on the standby database and write the following message in the alert log:

No standby log files of size <#> blocks available.

In sum, the most common cause of this error happens when your redo logs are not matching.