Re: Thread 1 cannot allocate new log

From: Steve Butler <sbut-is_at_seatimes.com>
Date: 1995/12/20
Message-ID: <Pine.SUN.3.91.951220091314.25888B-100000_at_seatimes>#1/1

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. Received on Wed Dec 20 1995 - 00:00:00 CET