Message-ID: <F001.005C9A88.20030808085424@fatcity.com>
Date: Fri, 08 Aug 2003 08:54:24 -0800
To: Multiple recipients of list ORACLE-L <ORACLE-L@fatcity.com>
Sender: ml-errors@fatcity.com
Reply-To: ORACLE-L@fatcity.com
Errors-To: ML-ERRORS@fatcity.com
From: Rajesh.Rao@jpmchase.com
Subject: Corrupt Inactive RedoLog Goup.
Organization: Fat City Network Services, San Diego, California
Precedence: bulk
Mime-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Members,

Production 8.1.6.3 database on Windows NT 4.0.

We noticed an entry in the alert log, citing that a log group could not be
archived since the 25th of July.. We have 3 log groups with 2 members each.
I notice that the 3rd redolog group has a status of Inactive with
Archived=No. This group has a sequence# of 745, while the other two have
advanced to 1073 and 1074 now.  We have had too many log switches since
then, and Oracle has chosen to ignore using this corrupt redo log group.
The database gets bounced daily, and opens without a problem, since this
group is not needed for instance recovery. I tried manual archiving.

SQLWKS> alter system archive log group 3;
ORA-16038: log 3 sequence# 745 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 1: 'F:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
SQLWKS> alter system archive log logfile 'F:
\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
     2> ;
ORA-16038: log 3 sequence# 745 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 1: 'F:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
SQLWKS> alter system archive log logfile 'G:
\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
     2>
     3> ;
ORA-16038: log 3 sequence# 745 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 1: 'F:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\TCP1\LOG3TCP1.ORA'

Similarly, it does not allow me to drop this member, saying it has not been
archived. Can I fake a recovery using cancel. and then open resetlogs? Or
if I put the database in noarchivelog mode, will Oracle let me drop this
corrupt redolog group?

Thanks
Raj


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: 
  INET: Rajesh.Rao@jpmchase.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).