When Standby Redo Log Group Fails

This could happen when you have a disk failure or user error (e.g. delete the standby log).

see sample error below. (VERIONS INFORMATION: 11.2.0.1 Red Hat 5u7)

  ERROR at line 1: ORA-00313: open failed for members of log group 4 of thread 1 ORA-00312: online log 4 thread 1: '/u01/app/oracle/oradata/stby/STBY/onlinelog/o1_mf_4_96qo85pl_.log' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3

Firstly, check if archived log are been transported to standby location and apply to the standby database.

Select max(sequence#) from v$archived_log # on primary and standby Databases.

Alter system switch logfile; #several times, on primary to force log archiving.

1. ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

2.  ALTER DATABASE CLEAR LOGFILE GROUP 7; OR ALTER DATABASE CLEAR LOGFILE 'FILENAME';

3.  ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;

4. ALTER DATABASE ADD STANDBY LOGFILE GROUP 7; OR ALTER DATABASE ADD STANDBY LOGFILE MEMBER '<PATH TO DELETED LOGFILE>' TO GROUP 7;

5. START REDO APPLY:  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

This procedure shows the necessary steps require to restore a lost standby redo group without recreating your standby database.