Jonathan Lewis wrote:
>
> You seem to have one hot block.
> The solution is to see if you can reduce the
> amount of data in that block so that the 'heat'
> can be spread over more blocks. (e.g. if it is
> a simple table block, would it be sensible to recreate
> it with PCTFREE = 90, to get fewer rows per block)
>
> However, your report seems to show 34.21 seconds
> of time lost in latching - how long has the system
> been running to clock up this time ? If the answer
> is several hours, then you don't really have a problem.
>
> --
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> Host to The Co-Operative Oracle Users' FAQ
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
> Author of:
> Practical Oracle 8i: Building Efficient Databases
>
> Screen saver or Life saver: http://www.ud.com
> Use spare CPU to assist in cancer research.
>
> Gulabchand Jaiswal wrote in message ...
> >Hello All,
> >oracle 8 .1.7.1.0 , OS : Solaris 8, app - pepolesoft portal database
> >
> >Extrmely hi latching event problem with cahce buffers chains
> >
> >The top event in statspack report is latch free %total wait time
> >is 88%.
> >Top 5 Wait Events
> >~~~~~~~~~~~~~~~~~ Wait % Total
> >Event Waits Time (cs) Wt Time
> >-------------------------------------------- ------------ ------------ ----
> ---
> >latch free 1,880 3,421 88.38
> >
> >
> >Latch activity for DB section shows following as troublesome :
> >
> >cache buffers chains 9,196,960 13.0 0.0 75 0.0
> >
> >drilled through v$latch, v$latch_children and x$bh as per oracle technote
> 61988.1
> >Was able to find that TCH for blk 5725 in file#12 is abnornally high i.e.
> 3390.
> >But that doc stops there. Does not tell how to fix it.
> >Any help will be apprciated.
> >
> >
> >Thx
He also might want to investigate FREELIST and FREELIST GROUPS for the
table/index.
--
Ron Reidy
Oracle DBA
Reidy Consulting, L.L.C.
Received on Thu Oct 25 2001 - 15:32:36 CDT
