[EMAIL PROTECTED]
cc:
Subject:Re: Buffer Busy Waits -- Sanity check please
Interesting. Any idea of what the point is in preventing other processes
from reading a block in the buffer?
Jared
On Saturday 01 December 2001 20:10, MacGregor, Ian A. wrote:
The P3 value of 130
Enabling parallel=2 or higher on this table could resolve the problem for
the original poster.
Regards,
Waleed
-Original Message-
Sent: Saturday, December 01, 2001 9:20 PM
To: Multiple recipients of list ORACLE-L
Malcolm,
The paragraph below would indicate that readers are
:
[EMAIL PROTECTED] Subject: Re: Buffer Busy Waits -- Sanity
check please
om
Interesting. Any idea of what the point is in preventing other processes
from reading a block in the buffer?
Jared
On Saturday 01 December 2001 20:10, MacGregor, Ian A. wrote:
The P3 value of 130 on the buffer busy waits does indicate that the block
is being read by another process as
Malcolm,
The paragraph below would indicate that readers are blocking.
Readers don't block in Oracle. The only reason I can think of at
the moment for a SELECT to cause buffer busy waits is delayed
block cleanout, of which there has been a lot of discussion lately.
I could be all mixed up
The P3 value of 130 on the buffer busy waits does indicate that the block is being
read by another process as Malcolm stated that's the process doing the scattered read
(Full table scan). Oracle needs to protect the block while it is being read. The
others sessions are waiting until the
Jeff,
The 3 sessions are doing the same (or similar) queries. In this case
count(*) which is forcing a full table scan of the table in each session.
The 3 sessions are thus trying to access the same blocks from the SGA, in
the same order. Only 1 session can access a block in the SGA at a
Kopie:
Gesendet von: [EMAIL PROTECTED]Thema: RE: Buffer Busy
Waits -- Sanity check please
]
ric.co.ukKopie:
Gesendet von: [EMAIL PROTECTED]Thema: RE: Buffer
Busy Waits -- Sanity check please
11/27/2001 09:25 AM
Bitte antworten an ORACLE-L
Jeff
Thomas Jeff wrote:
We recently had a new website go live. Since then, I'm seeing
constant buffer busy waits
and after a period of time, I see sessions hung on the same block#.
The SQL query
is always a COUNT(*) (below). It's almost as though one session has
a lock
of some sort in
: RE:
Buffer Busy Waits -- Sanity check please
Title: FW: Buffer Busy Waits -- Sanity check please
All: Thanks for the replies!
And yes, it's a data block. The query has been executed over 3,500 times
since this site went live about 5 days ago. I believe I'll check into
overindexing just as suggested, either that, go over and shoot
Title: Buffer Busy Waits -- Sanity check please
We recently had a new website go live. Since then, I'm seeing constant buffer busy waits
and after a period of time, I see sessions hung on the same block#. The SQL query
is always a COUNT(*) (below). It's almost as though one session has
Title: Buffer Busy Waits -- Sanity check please
Check
what segment owns this block: file# 72
block# 109177
This could
help finding the way to approach this problem.
-Original Message-From: Thomas Jeff
[mailto:[EMAIL PROTECTED]]Sent: Monday, November 26, 2001 6:21
PMTo
14 matches
Mail list logo
