Re: "Thread 1 cannot allocate new log" - error message

The LGWR can't cope.
You'll need to enlarge your online redolog files and/or add more.

A size of 5M per file is a good *minimum*, the Oracle default is 200k

Hth,
Sybrand Bakker, Oracle DBA

Mike Adams <mikea_at_best.com> schreef in berichtnieuws 3920d394$0$199_at_nntp1.ba.best.com...
> I keep getting the message "Thread 1 cannot allocate new log". This seems
> to occur when the database is under a load and switching the logfiles
> frequently. I've included output from the "alert" log.
>
> Anyone know what might be going on?? Could this be related to my previous
> post "shutdown immediate hung"
>
> thanks!!!
>
> PS. Please 'cc' mikea_at_best.com as I can't check newsgroups from work.
>
>
> GWR: prodding the archiver
> Thread 1 advanced to log sequence 706
> Current log# 2 seq# 706 mem# 0: /disk01/oracle/oradata/roctest/log02.log
> Mon May 15 18:33:57 2000
> ARC4: received prod
> ARC4: Beginning to archive log# 1 seq# 705
> ARC4: Completed archiving log# 1 seq# 705
> ARC4: re-scanning for new log files
> ARC4: prodding the archiver
> Mon May 15 18:33:58 2000
> ARC0: received prod
> Mon May 15 18:33:59 2000
> Thread 1 cannot allocate new log, sequence 707
> Checkpoint not complete
> Current log# 2 seq# 706 mem# 0: /disk01/oracle/oradata/roctest/log02.log
> LGWR: prodding the archiver
> Thread 1 advanced to log sequence 707
> Current log# 3 seq# 707 mem# 0: /disk01/oracle/oradata/roctest/log03.log
> Mon May 15 18:34:01 2000
> ARC1: received prod
> ARC1: Beginning to archive log# 2 seq# 706
> ARC1: Completed archiving log# 2 seq# 706
> ARC1: re-scanning for new log files
> ARC1: prodding the archiver
> Mon May 15 18:34:02 2000
> ARC2: received prod
> Mon May 15 18:34:04 2000
> LGWR: prodding the archiver
> Thread 1 advanced to log sequence 708
> Current log# 4 seq# 708 mem# 0: /disk01/oracle/oradata/roctest/log04.log
> Mon May 15 18:34:04 2000
> ARC3: received prod
>
>
>
>
Received on Tue May 16 2000 - 00:00:00 CDT