ORA-00313, ORA-00312, ORA-27037 in Standby Database [ID 601835.1]

最新推荐文章于 2024-12-19 20:08:47 发布

原创最新推荐文章于 2024-12-19 20:08:47 发布 · 9.3k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#database #oracle #file #thread #sql

Oracle Troubleshooting 同时被 3 个专栏收录

194 篇文章

订阅专栏

oracle常见故障解决方案

113 篇文章

订阅专栏

Oracle Data Guard

38 篇文章

订阅专栏

ORA-00313, ORA-00312, ORA-27037 in Standby Database [ID 601835.1]

	Modified 20-APR-2009 Type PROBLEM Status MODERATED

In this Document
  Symptoms
  Cause
  Solution
  References

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

Applies to:

Oracle Server - 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.

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;

References

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