Re: Alert: Thread 1 cannot allocate new log

It is true but certainly needs attention for future. Typically this can arise due to :

1: small redo log file size
2: fewer redo log groups
3: large batch jobs performing DML.

Suggestion:
1: If these errors are occuring regularly - RESIZE REDO LOGS ( increase the size)

2: Check the log switche interval - if too short - ( 5 min -15 min) , add a group ( default is two ).

3: If it occurs during batch jobs, increase the size and groups. ( this situation needs less attention )

Ramanarao chamarty
rchamart_at_temple.edu

Terry Dykstra (tdykstra_at_cfol.ab.ca) wrote:
: It is harmless. It just slows down the system. The easiest solution is to
: make your logs a bit larger.
:
: --
: Terry Dykstra
: Canadian Forest Oil Ltd.
: See you at Techwave 99: http://www.sybase.com/events/techwave99/
: Bryan M. Kramer wrote in message <37B18C3B.F69C253A_at_techne.ca>...
: >I'm running oracle 8 on an NT server.
: >
: >I have a system that is mysteriously and not repeatably missing
: >records in the database that we expect to see after a run of the
: >complete application. Running the component individually seems to
: >indicate
: >that there is no problem with the application. The only anomoly is that
: >
: > Current log# 5 seq# 258490 mem# 0:
: >/oracle06/oradata/dev2/redodev205.log
: >Thread 1 cannot allocate new log, sequence 258491
: >Checkpoint not complete
: >
: >messages are appearing in the alert log. A search of deja news shows
: >some
: >discussion on this topic which imply that the message is a harmless
: >warning.
: >
: >Is this really the case? Is it possible that the inserts and updates are
: >NOT being
: >committed for some reason?
: >
: >Thanks
: >--
: >Bryan M. Kramer, Ph.D., Software Architect
: >Techné Knowledge Systems Inc.
: >439 University Ave., Suite 900, Toronto ON M5G 1Y8
: >416-977-3960 fax 416-977-9902 www.techne.ca
: >
: >
:
:
Received on Wed Aug 11 1999 - 10:58:18 CDT