SMON Trace File Meaning

From: <sharmp_at_hhcs.gov.au>
Date: 5 Feb 93 14:06:39 +1100
Message-ID: <1993Feb5.140639.614_at_hhcs.gov.au>

We have had complaints from users that one of our databases was taking over 30 minutes to commit a single transaction between 5.00 and 6.35 last night. There seems to have been no problems with comms or the machine. The only thing I can find that I don't understand is the SMON trace file below. Does anyone know what caused the last two lines?

Dump file $1$DUA24:[DBA.TRACE]SRV_PRD6B_005.trc  2-FEB-1993 22:34:17.21
ORACLE V6.0.34.0.0 - Production vsnsta=0 Proc: 0x20a09d79 ORA_PRD6B_SMON User: [21303,001] ORACLE Term: Image: STA204:[DBA.KERNEL.ORA_PRODUCTION.RDBMS]SRV.EXE;3 Enqueue Quota: 512

vsnrcf=6.0.23.0.0 vsnwcf=6.0.30.3.0 vsnrdb=6.0.23.0.0 vsnwdb=6.1.27.2.0
vsnrlg=6.1.27.0.0 vsnwlg=6.1.27.3.0 vsnclp=6.0.23.0.0 vsnplp=6.0.30.3.0
vsnsql=1 vsnxtr=0
cpu 9XXX E04108B vms V5.5-2   clustered with 5 nodes
scsnd: CNB12V  , ndname: CNB12V, sys$node CNB12V::                        

cpuid E rev 00B20000000000040E04108B archflg 338D0 hwmdl: 178 hwnm: VAX 9000-410 cpus: FFFFFFFF cpush: 0 active: 1, avail: 1 locktbl size 20000 max 65535 resource hash size 16384

SMON: system monitor started
 4-FEB-1993 18:47:04.62 *** obviously this is the time *** SMON: system monitor process posted *** posted what? ***

Many thanks

Peter  

---

Peter Sharman                                                 SHARMP_at_HHCS.GOV.AU
Aust. Dept Health, Housing and Community Services             06-289 7661


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Received on Fri Feb 05 1993 - 04:06:39 CET