Re: ora-00340 -Please Help

In our last gripping episode aminocha_at_unibiz.com wrote:
> Hi,
> I am running oracle 8.0.5 on windows NT. A cold backup is scheduled
> every night and the database is brought back up after that.
> Every morning when i come to work I see that the database is not up (
> services not started). I reboot the server and the database opens.
>
> As I am a newbee i am unable to figure out why this is happenning.I
> opened the alert files and found that ora-00340 error has occurred.
> what does this mean and how do i fix this problem.
>
> Below is the sample error message which i am getting.
>
> Any help will be greatly appreciated. Thanks in advance.
>
> Anurag
>
> Database mounted in Exclusive Mode.
> Completed: alter database "r2" mount exclusive
> Wed Dec 27 07:37:51 2000
> alter database "r2" open
> Beginning crash recovery of 1 threads
> Recovery of Online Redo Log: Thread 1 Group 4 Seq 1399 Reading mem 0
> Mem# 0 errs 0: D:\ORADATA\R2\R2_REDO_4.LOG
> Crash recovery completed successfully
> Picked broadcast on commit scheme to generate SCNs
> Wed Dec 27 07:37:52 2000
> Thread 1 advanced to log sequence 1400
> Thread 1 opened at log sequence 1400
> Current log# 5 seq# 1400 mem# 0: D:\ORADATA\R2\R2_REDO_5.LOG
> Successful open of redo thread 1.
> Wed Dec 27 07:37:52 2000
> SMON: enabling cache recovery
> SMON: enabling tx recovery
> Wed Dec 27 07:37:53 2000
> Completed: alter database "r2" open
> Wed Dec 27 08:25:16 2000
> LGWR: terminating instance due to error 340
> Wed Dec 27 08:25:17 2000
> Errors in file D:\ORAADMIN\R2\UDUMP\ORA00162.TRC:
> ORA-00340: IO error processing online log of thread
>
> Wed Dec 27 08:25:22 2000
>
> Sent via Deja.com
> http://www.deja.com/
>

It would appear that you have a bad redo log file. This may be a disk error since you can eventually start the instance. Check the various trace files to determine which redo log is causing the problem. If they are all on the same disk and one redo log is not repeatedly listed it is most likely a disk problem (bad blocks). You may need to drop the redo log files and re-create them on a different disk (the database will be running when you do this), or replace the disk and recover the redo logs from a database backup (you will need to shut the database down to do this).

In order to replace the redo logs while the database is running you will need to query the V$LOG and V$LOGFILE views:

select f.member, l.status
from v$log l, v$logfile f
where l.group# = f.group#

This will report which logfile is still active; all inactive logfiles can be dropped and re-created.

--
David Fitzjarrell
Oracle Certified DBA


Sent via Deja.com
http://www.deja.com/