Re: Thread 1 cannot allocate new log

From: Ken Friday <ken.friday_at_teldta.com>
Date: 1995/12/19
Message-ID: <4b6i50$p6_at_madison.tdsnet.com>#1/1

chuckh_at_ix.netcom.com (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
>
>--
>Chuck Hamilton
>chuckh_at_ix.netcom.com
>
>Never share a foxhole with anyone braver than yourself!
>
It means you experienced a log switch (redo log). "Thread" makes more sense in a parallel server environment where each instance is associated with a collection of redo log via a thread. Received on Tue Dec 19 1995 - 00:00:00 CET

This message: [ Message body ]
Next message: Bill Beaton: "Oracle 7.2.2.3 memory leak"
Previous message: Paul Roberts: "Re: YEAR 2000 Problem with existing Databases"
In reply to: Chuck Hamilton: "Thread 1 cannot allocate new log"
In reply to Chuck Hamilton: "Thread 1 cannot allocate new log"
Next in thread: Fernand St-Georges: "Re: ODBC"
Reply: Steve Butler: "Re: Thread 1 cannot allocate new log"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message