OT: RE: Understanding AWR 'buffer waits'
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <tim@xxxxxxxxx>, <nkodner@xxxxxxxxx>
- Date: Wed, 24 Mar 2010 08:40:48 -0400
Of course it is also natural that anything having to do with the CUBS waits
forever. Isn't there some sort of goat involved?
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Tim Gorman
Sent: Tuesday, March 23, 2010 12:31 PM
To: nkodner@xxxxxxxxx
Cc: oracle-l-freelists
Subject: Re: Understanding AWR 'buffer waits'
<snip>
But, once I find such statements I'd check to see if they are
accessing/manipulating tables within the CUBS_DATA tablespace, and then use
"select * from table(dbms_xplan.display_awr('sql-id'))" to get the execution
plan(s), and then look for something ineffective within the execution plan.
<snip>
http://www.neilkodner.com/images/skitch/buffer_waits-20100323-105423.jpg
Certain tablespaces (cubs_data) have far more buffer waits, compared to
others, even others(uworks_misc_index) with a higher amount of reads and
writes.
Our datafiles for each of the tablespaces are equally distributed across 3
volumes on a SAN.
How can i interpret the buffer waits and explain them in order to
potentially identify a problem?
-- //www.freelists.org/webpage/oracle-l
Other related posts:
- » OT: RE: Understanding AWR 'buffer waits' - Mark W. Farnham
