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 Database - Enterprise Edition - Version 9.2.0.7 to 11.2.0.2
[Release 9.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 25-JUN-2013***
Symptoms
SQL> alter database drop standby logfile group 1;
alter database drop standby logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: '/oradata/fs32/redo0101'
ORA-00312: online log 1 thread 1: '/oradata/fs37/redo0102'
Changes
Cause
1. Standby_file_management does not affect Online RedoLogs.
2. Thee Online RedoLog which is
being dropped on the Primary is either the current Online RedoLog
or it has not completely been archived yet.
See Oracle Data Guard, Concepts and Administration, Release 2
(9.2), Part No. A96653-02,
Chapter 11: Initialization Parameters ->
STANDBY_FILE_MANAGEMENT
You can verify this if you have a look at V$LOG
-> The Status should be 'INACTIVE' for the RedoLog to be
dropped.
Solution
To implement the solution, please execute the following steps:
1) Switch the logfile on primary so that group can become
non-current.
connect / as sysdba
alter system switch logfile;
2) Copy from primary to standby.
If you are working with Group 1 on the primary
then copy both files for group 1 from the primary
to the standby machine into an alternate location at operating
system level.
3) Move current group one files on the standby to a different
location
4) Rename the logfile- Move the copied redo logs
into the group 1 current location
ALTER DATABASE RENAME FILE
'/FULL_PATH_OF_OLD_LOCATION/AND_REDO_LOG_NAME.LOG'
TO
'/FULL_PATH_OF_NEW_LOCATION/AND_REDO_LOG_NAME.LOG';
5) Clear the logfile :
alter database clear logfile group;
6)
alter database drop standby logfile group1 .