Re: Thread 1 cannot allocate new log

From: Sue Trombley <stromble_at_wnet.gov.edmonton.ab.ca>
Date: 1995/12/21
Message-ID: <DJy2Dx.p9_at_champ.wnet.gov.edmonton.ab.ca>#1/1


In article <Pine.SUN.3.91.951220091314.25888B-100000_at_seatimes>,

   Steve Butler <sbut-is_at_seatimes.com> wrote:
>On Mon, 18 Dec 1995, Chuck Hamilton wrote:
>> What does this message mean in the alert log? I've been getting a log
>> of them lately.
>>
>> Fri Dec 15 11:57:01 1995
>> Thread 1 advanced to log sequence 482
>> Current log# 2 seq# 482 mem# 0:
>> /usr/oracle/product/7.1.6/control/log2drda.dbf
>> Current log# 2 seq# 482 mem# 1: /usr/ORACLE/CONTROL/log2drdb.dbf
>
>Hmm, you didn't include that error message in the portion of the log you
>copied off. I can't tell whether it's:
>1. the archiver complaining because of disk space at the destination
> (when it's copying redo logs); or,
>2. all the redo logs are currently not-available (ie, the oldest redo log
> still hasn't been fully checkpointed.
>3. something else!
>
>The solution depends on more information. How about a larger snippet
>from the alert log?
>
>
>+----------------------------------------------------+
>| Steve Butler Voice: 206-464-2998 |
>| The Seattle Times Fax: 206-382-8898 |
>| PO Box 70 Internet: sbut-is_at_seatimes.com |
>| Seattle, WA 98111 Packet: KG7JE_at_N6EQZ.WA |
>+----------------------------------------------------+
>All standard and non-standard disclaimers apply.
>All other sources are annonymous.
>
We are receiving a similar error in our alert log. This is information that is in our log & it keeps repeating itself over & over. The messages appear when we are in the process of updating snapshots on our database. I assume that the error relates to #2 that the redo logs can't be checkpointed but is there something we can change to stop these messages from appearing in the log ? Any help is much appreciated !

  Current log# 3 seq# 62784 mem# 0: /u07/ORACLE/PA/log3aPA.dbf   Current log# 3 seq# 62784 mem# 1: /u06/ORACLE/PA/log3bPA.dbf Thread 1 advanced to log sequence 62785   Current log# 1 seq# 62785 mem# 0: /u07/ORACLE/PA/log1aPA.dbf   Current log# 1 seq# 62785 mem# 1: /u06/ORACLE/PA/log1bPA.dbf Thread 1 advanced to log sequence 62786   Current log# 2 seq# 62786 mem# 0: /u07/ORACLE/PA/log2aPA.dbf   Current log# 2 seq# 62786 mem# 1: /u06/ORACLE/PA/log2bPA.dbf

Thread 1 cannot allocate new log, sequence 62787              
Checkpoint not complete                                       
  Current log# 2 seq# 62786 mem# 0: /u07/ORACLE/PA/log2aPA.dbf   Current log# 2 seq# 62786 mem# 1: /u06/ORACLE/PA/log2bPA.dbf Thread 1 advanced to log sequence 62787   Current log# 3 seq# 62787 mem# 0: /u07/ORACLE/PA/log3aPA.dbf   Current log# 3 seq# 62787 mem# 1: /u06/ORACLE/PA/log3bPA.dbf

Thanks,
Sue Trombley Received on Thu Dec 21 1995 - 00:00:00 CET

Original text of this message