Re: alert_SID.log -> cannot allocate new log, sequence x

Jonas Heyman (jonas_at_sth.ifsab.se) wrote:
: Hi,
 

: I'd experienced the following error in alert_SID.log:
 

: Thread 1 cannot allocate new log, sequence 3161
: Checkpoint not complete
 

: It happens while there are a lot of jobs and transactions going on.
: Also the database seems to hang and does a lot of internal job.
 

: 1. Should I add more logfiles ?
: 2. Should the logfiles be larger of size ?
: 3. Should I do a checkpoint more often or should
: they occour at logswitch ?
 

: I'm not sure what the problem is, have anyone experienced it.
: I'll be glad to get a explanation and how to fix it.
 

: Thanks in advance,
 

: Sincereley Jonas.
 

: johe_at_sth.ifsab.se

You should add more log files. The problem is that you have filled all of you logfiles. A log file can not be freed up until its checkpoint has finished. Larger log files will reduce the time between delays but probably make the delays longer. Checkpointing more often would help but probably 'normal' processing times would suffer.

      Nick

--
                                  _____________
    Nick Strange                      churchill        Tel: +44 81 313 5679
    Head of IT                    =============        Fax: +44 81 313 5699
    Churchill Technology
    15-17 London Rd, Bromley BR1 1DE, UK.    Email: nicks_at_churchill.co.uk