Re: Thread 1 cannot allocate new log

It means your logs are grinding the disk too fast and checkpointing is not able to keep up. The obvious solution could be to add more redo log group(s) with each member sized atleast about n/2 times the current size ( where n is the no of times you saw the message in the log, from the start and end of the application install ). This is not a sizing metrics but some values to start with.

Here are some metal lines ( obviously from Oracle )

Redo logs should switch approximately every 30 minutes. If they switch
sooner, look at the time between switches.  

For example:  

   a.) If your time between switches is 10 minutes, you need to

       increase the size of redo log files three times.  

   b.) If your time between switches is 15 minutes, you need to

       increase the size twice.  

   c.) If the switch time is more than 30 minutes, it means there is

       not much activity on the database and it's OK.  

HTH,
Vinayak

Anne Williamson <annew_at_mac.com> wrote in message news:<3B1C4BC6.A8B58763_at_mac.com>...
> Yesterday I was doing a schema update on my test database, using scripts
> supplied by the third party who supplies the end-user application.
> Looking at the alert log I noticed a number of messages like this:
>
> Thread 1 cannot allocate new log, sequence 1609
> Checkpoint not complete
>
> There is no Oracle error message reported. I couldn't find anything
> about it in the Oracle error messages manual. The scripts all seemed to
> complete happily.
>
> Does anyone know what is causing these messages? How do I stop them?
> What is the result of these incomplete checkpoints?
>
> Digital Unix 4.0F, Oracle 8.0.5.1.1
>
> Many thanks in advance
Received on Tue Jun 05 2001 - 10:53:43 CDT