Re: Tuning: What causes "Thread 1 cannot allocate new log" ?

Hi John,
This error arises becos LGWR cannot write into the RedoLog file either becos the CheckPoint triggered earlier is not complete or ARCHiver did not finish copying the filled Redo Log file to the LOG_ARCH_DEST.

You can alleviate this problem by
1) Add more Redo Log files as this will provide more time for the CHeckPoint to Complete as well as more time for the Archiver to complete the File Copy 2) If this is a Archiver issue , Accelerate it by tuning LOG_ARCHIVE_BUFFERS setting in init.ora
3) You may also need to Increase the Size of the Redo Log file, if this is a 'High Transaction Volume' issue . I have seen this error many times during High Data Loads and Resizing the redo Log files definetely helped..

Hope this helps..

-Thiru

John Haskins wrote:

> Greetings, helpful folks:
>
> I've been tuning an Oracle 7.3.4 instance running on Solaris 2.6 and have
> run into an error in the instance's alert log that I cannot eliminate. The
> message is:
>
> Thread 1 cannot allocate new log, sequence 4331
>
> Since theer is no number at the beginning of this message, I haven't had a
> lot of luck finding it in the Oracle online documentation. I did use the
> Java-based search function, but it continually crashed. A search of .htm
> files in the Docs directory using the criteria "cannot allocate new log"
> produced no hits.
>
> I'd appreciate any assistance anyone can provide. Whatever is causing this
> problem is also cutting throughput to about 1/10th of normal on the INSERT
> batch where it occurs.
Received on Tue Aug 24 1999 - 14:24:04 CDT