Hi Sri,
If you can identify the segments involved from the p1 and p2 parameters and put
those segments into a KEEP buffer pool you should be able to get a lot of
relief. Failing that, or if they are too big, consider either increasing
db_block_buffers if you can or setting
Hi Steve,
A couple questions: whihc p3 value is the value that indicates a need to
increase freelists? Are there any plans to adapt your freeliusts estimation
script for tables for indexes as well, or pointers on how to do so (I think
I can do a direct port to work off dba_indexes, butparts of
We've lot buffer busy waits in data block with P3 value 130 in V$session.
I've read about this in few notes, but still I do not understand few things.
P3=130 means:
-
Block is being read by another session and no other
suitable block image was found, so we wait until the read
