ORA-00313, ORA-00312, ORA-27037 in Standby Database

ORA-00313, ORA-00312, ORA-27037 in Database [ID 601835.1]
		修改時間20-APR-2009     型別PROBLEM     狀態MODERATED

In this Document
  
  
  
  

---

This document is being delivered to you via Support's(RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.4
This problem can occur on any platform.

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.

If you are using pfile then set the parameter in init file after shutting down the database:

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:

3.  Execute the command to clear all log groups on standby for each log group (for each log group):

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)

 (b) Recreate the standby logfile group(s)

References

- DATAGUARD ERROR IN 10.2
- Standby Redo Logs are not Created when Creating a 9i Guard DB with RMAN
- ORA-19527 reported in 10gR2 Standy database