Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Cannot allocate new log - checkpoint not complete

RE: Cannot allocate new log - checkpoint not complete

From: Reardon, Bruce (CALBBAY) <>
Date: Thu, 03 Apr 2003 17:28:04 -0800
Message-ID: <>

There are some other effects I can think of.

Up to you if these are important / significant to your users.

If you make them bigger and you have a standby database then the standby might end up being further behind production (unless you have a script to workaround this) and also in this case you may then not get the files transferring successfully (depends on your network etc).

Also, if you make them bigger and you have a loss of all redo logs (hopefully unlikely if they are mirrored on mirrored disks) then you will lose more data as it will be a longer period of time since the last archive log was created.

And what about your archive log management scripts - do they keep x days worth of files (in which case the volume of archive log on disk will not change) or do they keep y files - in this case the volume of disks would increase unless the script(s) are altered.

Bruce Reardon

-----Original Message-----

Sent: Friday, 4 April 2003 3:44 AM
To: Multiple recipients of list ORACLE-L


The only potential disadvantage is that recovery will take longer when bringing up the database after a crash.

Jay Miller

-----Original Message-----

Sent: Thursday, April 03, 2003 9:39 AM
To: Multiple recipients of list ORACLE-L

        I dissagree, they will be bigger but there will be less of them. If the amount of processed data does not change, I do not think changing the size of the redolog files should affect the total amount fo bytes to be backeup up

        Thanks for the recommendation anyway ;)



-----Mensaje original-----

De: []En nombre de Stefan Jahnke Enviado el: jueves, 03 de abril de 2003 15:44 Para: Multiple recipients of list ORACLE-L Asunto: AW: Cannot allocate new log - checkpoint not complete


I would suggest to increase the redo log size. Doesn't effect you during daily operation, but prevents the database from hanging during nightly batches. No side effects I can think of (except for the fact that, of course, it will take you longer to backup the archived logs since the files are bigger, duh ;).

Good luck

Stefan Jahnke
BOV Aktiengesellschaft
Voice: +49 201 - 4513-298
Fax: +49 201 - 4513-149
Please remove nospam to contact me via email.

visit our website:
subscribe to our newsletter:

Sicherheitsluecken mit IT-Security-Konzepten von BOV effizient schliessen! Weitere Informationen unter +49 201/45 13-240 oder E-Mail an

Wie Sie wissen, koennen ueber das Internet versandte E-Mails leicht unter fremden Namen erstellt oder manipuliert werden. Aus diesem Grunde bitten wir um Verstaendnis dafuer, dass wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen und Aeusserungen ausschliessen.

As you are probably aware, e-mails sent via the Internet can easily be copied or manipulated by third parties. For this reason we would ask for your understanding that, for your own protection and ours, we must decline all legal responsibility for the validity of the statements and comments given above.

-----Ursprüngliche Nachricht-----

Von: Fermin Bernaus Berraondo [] Gesendet: Donnerstag, 3. April 2003 10:04 An: Multiple recipients of list ORACLE-L Betreff: Cannot allocate new log - checkpoint not complete

        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
Telf. +34 - 943 157 331
Fax +34 - 943 151 276
Please see the official ORACLE-L FAQ:
Author: Reardon, Bruce (CALBBAY)

Fat City Network Services    -- 858-538-5051
San Diego, California        -- Mailing list and web hosting services

To REMOVE yourself from this mailing list, send an E-Mail message to: (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).
Received on Thu Apr 03 2003 - 19:28:04 CST

Original text of this message