Prev: Installation of Oracle patch p5337014_10203_LINUX.zip on linux.
Next: Slow connection to Oracle 10
From: Shakespeare on 23 Aug 2008 15:19 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
From: Mladen Gogala on 24 Aug 2008 10:21 On Sat, 23 Aug 2008 21:19:36 +0200, Shakespeare 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 Something like that should be recorded in the alert log. Posting the relevant information from the alert log would certainly help people on this group during the diagnostic process. -- http://mgogala.freehostia.com
From: louis.szarzec on 25 Aug 2008 06:07 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...(a)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
From: Shakespeare on 25 Aug 2008 06:17 <louis.szarzec(a)ggzdrenthe.nl> schreef in bericht news:0bfd342d-7ba1-4f18-8ba3-6b002343c840(a)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...(a)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 > Hello Louis, this looks EXACTLY like our problem! We'll investigate this, and will report here! Shakespeare
From: Shakespeare on 25 Aug 2008 06:25 "Mladen Gogala" <mgogala(a)yahoo.com> schreef in bericht news:48b16e63$0$15596$834e42db(a)reader.greatnowhere.com... > On Sat, 23 Aug 2008 21:19:36 +0200, Shakespeare 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 > > Something like that should be recorded in the alert log. Posting the > relevant information from the alert log would certainly help people on > this group during the diagnostic process. > > > > -- > http://mgogala.freehostia.com This is the part of the alert log: > 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 Thanks, Shakespeare
|
Next
|
Last
Pages: 1 2 3 Prev: Installation of Oracle patch p5337014_10203_LINUX.zip on linux. Next: Slow connection to Oracle 10 |