Re: Data block and buffer busy quite high, suggestions?

Notes in-line.

-- 
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person
  who can answer the questions, but the
  person who can question the answers -- T. Schick Jr


Next public appearances:
 March 2004 Hotsos Symposium - Keynote
 March 2004 Charlotte NC - OUG Tutorial
 April 2004 Iceland


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___February


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"Brian Peasland" <dba_at_remove_spam.peasland.com> wrote in message
news:400FDAB2.DFAB64B4_at_remove_spam.peasland.com...
>


> Then I'd take the author's (D. Burleson) approach to heart, "The main

> way to reduce buffer busy waits is to reduce the total I/O on the

> system. This can be done by tuning the SQL to access rows with fewer

> block reads."


I don't think that applies in this case.  The wait for another
session to complete its read is a 1013 in the earlier versions
of Oracle (130 in later versions), not 1016.

Also, 130's (or 1013's) are most commonly the result of
excessive I/O from tablescans - the probability of getting
them from indexed access paths is relatively low; and I
would guess that the OP would have been asking about
tablescans before asking about buffer busy waits if his
system was showing excessive tablescans.