Open failed for members of log group

Question

HI,
OS : LINUX 5.1
DB : 10.2.0.3
i have configured physical standby and its working fine. but in alert log i m getting below error.
i have checked the physical location of member. it is very much available.
Mon May 24 23:54:19 2010
Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon May 24 23:54:19 2010
Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u001/app/oracle/oradata/YAHOO/redo01.log
Clearing online log 1 of thread 1 sequence number 31
Mon May 24 23:54:19 2010
Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon May 24 23:54:19 2010
Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
can any one suggest?
Regards,
BK

Answer 1

Hi,
Below note was taken from metalink;
Symptoms
Following errors in alert.log of standby database during startup of the standby database:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/oradata/prod/redo01b.log'
ORA-27037: unable to obtain file status
Cause
Online Redo logs missing on standby database.
Solution
You can safely ignore these messages. Online redo logs will be created automatically when you activate the standby after switchover or failover.
If you want to fix these messages then please use following steps:
1. Check and set "log_file_name_convert" parameter if the location of log files are different on primary and standby.
SQL> alter system set log_file_name_convert = "'<location on primary>','<location on standby>'" scope=spfile;
If you are using pfile then set the parameter in init file after shutting down the database:
*.log_file_name_convert = '<location on primary>','<location on standby>'
For 10gR2 only : Set this parameter even if the location of the redo logs are same on both primary and standby otherwise you may get ORA-19527 and ORA-312 while or after implementing the below steps.
This is due to internal bug in 10.2.
2. Cancel Managed Recovery process on the standby:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3. Execute the command to clear all log groups on standby for each log group (for each log group):
SQL>alter database clear logfile group 1;
4. Check the v$log view to confirm the size and status.
5. Recreate standby redo logs on standby (only if standby Redo logs are also missing) using:
(a) Drop the standby redo logfile group(s) (check v$standby_log)
SQL> alter database drop standby logfile group 4;
(b) Recreate the standby logfile group(s)
SQL> alter database add standby logfile group 4 ('/u03/redo/stby01.log') size 50m;
Hope it helps you.