Title: RE: cache buffer chains contention
Would it seem likely for Oracle to be
doing ANYTHING for a full 30 seconds
without hitting another wait?
Matt Adams - GE Appliances - [EMAIL PROTECTED]
Reason is 6/7ths of treason. - The Xtals
-Original Message-
From: Jonathan Lewis
The Xtals
-Original Message-
From: Jonathan Lewis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 6:54 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: cache buffer chains contention
seconds_in_wait increments every three seconds,
so if State is anything other than WAITING
It's certainly possible for Oracle to be pushed
into very heavy CPU usage, particularly for
PX slaves, but even in serial queries.
Two common 'causes' are queries with
correlated sub-queries against small tables;
and queries which have been over-indexed
and hinted to avoid table-scans.
Title: cache buffer chains contention
Ok, some guru please explain this to me.
process is waiting for 'latch free' according to
v$session_wait and the value of P2 = 26
which is the cache buffer chains latch.
(while holding the HW enqueue, with a bunch of
processes waiting on HW)
State
seconds_in_wait increments every three seconds,
so if State is anything other than WAITING the
column tells you how much time has passed
since the last wait completed. (Contrary to the
urban legend that says the value is meaningless).
There are various anomalies and oddities about
wait
-
De: elain he [SMTP:[EMAIL PROTECTED]]
Enviado el: mircoles 28 de febrero de 2001 0:31
Para: Multiple recipients of list ORACLE-L
Asunto: cache buffer chains contention
Does anyone have any advice on reducing cache buffer chains latch
contention?
From v$latch_children, I found the ch
