ORA-00313,ORA-00312,ORA-27037,ORA-19527 DATAGARD 11G r2

<pre>
sys@icmedg>select db_unique_name,PLATFORM_NAME,database_role from v$database;
DB_UNIQUE_NAME                 PLATFORM_NAME                  DATABASE_ROLE
------------------------------ ------------------------------ ----------------
ICMEDG                         Linux x86 64-bit               PHYSICAL STANDBY
sys@icmedg>select * from v$version where rownum=1;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
</pre>
--## following errors from alert file
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oracle/oradata/icme/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 312' was flood controlled (0x5) (no incident)
ORA-00312: online log 2 thread 1: '/oracle/oradata/icme/redo02.log'
Error 19527 creating/clearing online redo logfile 2
*** 2013-10-12 01:12:09.007 4320 krsh.c
refer MOS
Cause
This is in fact an Enhancement to the Data Guard Technology introduced in 10.2.0.
The Goal here is to improve speed of Switchover and Failover. In previous Versions a Role Transition would require to clear the Online Redo Logfiles before it can become a Primary Database.  Now we attempt to clear the Online Redo Logfiles when starting Managed Recovery.
If the Files exist then they will be cleared, but if they do not exist we report the Error, attempts to create the Online Redo Logfiles and starts Recovery. Even if this is not possible because of different Structure and log_file_name_convert is not set, MRP does not fail; it only raises these Errors.
As an extra Enhancement if the Online Redologs do exist you must specify the log_file_name_convert Parameter even if there is no difference in the Name. This has been implemented to reduce the chances that the Primary Online Redologs are cleared when MRP starts.  It is the equivalent of asking - Are you sure you want the logs to be called this....
If the log_file_name_convert parameter is not set then the ORA-19527 is reported and the log file is not cleared at this time..
Solution
Solution
to stop both of these errors is to ensure log_file_name_convert is set correctly.