Re: Database in quiesce mode

From: <louis.szarzec_at_ggzdrenthe.nl>
Date: Mon, 25 Aug 2008 03:07:39 -0700 (PDT)
Message-ID: <0bfd342d-7ba1-4f18-8ba3-6b002343c840@79g2000hsk.googlegroups.com>


Hallo Shakespeare,

We have the same problem, last week we have upgraded to 10.2.0.4 on AIX 5.2 64 bit.
And at the moment we have already 2 times a quiesce mode. In the alert log is written:
Mon Aug 25 11:21:09 2008
Thread 1 advanced to log sequence 3080 (LGWR switch)

  Current log# 3 seq# 3080 mem# 0: /oradata/xmcp/redo03.log
  Current log# 3 seq# 3080 mem# 1: /oradata/xmcp/redo03b.log
  Current log# 3 seq# 3080 mem# 2: /oradata/xmcp/redo03c.log
Mon Aug 25 11:44:11 2008
Database in quiesce mode
Mon Aug 25 11:48:39 2008
Thread 1 advanced to log sequence 3081 (LGWR switch)
  Current log# 2 seq# 3081 mem# 0: /oradata/xmcp/redo02.log
  Current log# 2 seq# 3081 mem# 1: /oradata/xmcp/redo02b.log
  Current log# 2 seq# 3081 mem# 2: /oradata/xmcp/redo02c.log
Mon Aug 25 11:50:29 2008
Database out of quiesce mode

LouisDBA.

On 23 aug, 21:19, "Shakespeare" <what..._at_xs4all.nl> wrote:
> I have a client using 10.2.0.4 64 bit on AIX.
> After an upgrade from 9 to 10, his database went (after running for about 15
> hours) into quiesce mode without anyone specifically performing such an
> action. (Unfortunately, no more specific data available right now; only
> thing he noticed in the alert log was a log writer switch on redo01.log when
> this happened).
> After a while, his db went unquiesce again. I searched docs, metalink,
> Google but did not find a clue why a DB would do this all by itself.
> A) Is this possible anyway?
> B) What could cause this?
>
> Thanks,
>
> Shakespeare
Received on Mon Aug 25 2008 - 05:07:39 CDT

Original text of this message