I think I am having problems with my redologs. Under normal circumstances no
errors arise, but if I do a massive import of data as I was doing last night, this is
what alertSID.log shows from time to time:
Wed Apr 2 23:29:52 2003
Thread 1 advanced to log sequence 557295
Current log# 3 seq# 557295 mem# 0: /baandata/oradata/baan/redobaan03.log
Wed Apr 2 23:31:11 2003
Thread 1 cannot allocate new log, sequence 557296
Checkpoint not complete
Current log# 3 seq# 557295 mem# 0: /baandata/oradata/baan/redobaan03.log
Wed Apr 2 23:31:50 2003
In that exact time, everything freezes and the database is dead until a new
redolog can be used.
I have 3 redologs 50 Mb each. I've read that the error is because too much
data is trying to get into the redologs and all of them are full, Oracle does not have
the time to reuse a redolog and has to wait until the redolog is ready to be reused.
So the solution seems to make these redolog files bigger or to create new
ones. What are the side effects of one or the other? will performance under normal
work be penalised?
..............................................
Fermín Bernaus Berraondo
Dpto. de Informática
SAMMIC, S.A.
[EMAIL PROTECTED]
http://www.sammic.com
Telf. +34 - 943 157 331
Fax +34 - 943 151 276
..............................................
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Fermin Bernaus Berraondo
INET: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] (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).
