Message-Id: <10595.115051@fatcity.com>
From: Ronen Levit <RonenL@talmai.com>
Date: Sun, 20 Aug 2000 15:13:06 +0200
Subject: Redolog problem - Anyone?

Hi all,

While running in multi-thread processes that performs loading and inserting
using SQL*Loader and some PL/SQL (in all 4 threads), I got the following
error, and the Oracle got stuck. It is on a development database, and
occured during the night of the weekend.
When we first noticed that, after couple of hours, we tried to login the
system but the logins hanged on and were stuck too.

Looking for some help on that. Why it happened and how can we prevent such
errors in the future?

I've read in some earlier threads in the news that its an unexpected error
that sometimes might happen ... sounds awful.

Fri Aug 18 02:52:08 2000
Thread 1 advanced to log sequence 88813
  Current log# 1 seq# 88813 mem# 0: S:\ORACLE\ORADATA\CLEODB\REDO01.LOG
  Current log# 1 seq# 88813 mem# 1: S:\ORACLE\ORADATA\CLEODB\REDO02.LOG
Fri Aug 18 02:52:26 2000
Thread 1 advanced to log sequence 88814
  Current log# 3 seq# 88814 mem# 0: S:\ORACLE\ORADATA\CLEODB\REDO05.LOG
  Current log# 3 seq# 88814 mem# 1: S:\ORACLE\ORADATA\CLEODB\REDO06.LOG
Fri Aug 18 02:52:43 2000
Thread 1 cannot allocate new log, sequence 88815 <-----
Checkpoint not complete
  Current log# 3 seq# 88814 mem# 0: S:\ORACLE\ORADATA\CLEODB\REDO05.LOG
  Current log# 3 seq# 88814 mem# 1: S:\ORACLE\ORADATA\CLEODB\REDO06.LOG
Dump file D:\Oracle\admin\Cleodb\bdump\cleodbALRT.LOG 

Ronen Levit
Database group manager
Talmai
Tel:  +972 8 9460606 #212
Fax:  +972 8 9460705