Re: Help me read my statspack report

emdproduction_at_hotmail.com wrote:
> >
> > Generally speaking you should resolve the issue, instead of curing
> > symptoms.
> > Just upgrading the hardware seldomly helps.
> >
> > Cache buffer chain problems are usually the result of tuning a database
> > by increasing the buffer cache, instead of tuning inefficient
> > statements.
> >
> > --
> > Sybrand Bakker
> > Senior Oracle DBA
>
> Sybrand,
>
> Thanks very much for your help.
>
> But from Johnathan's previous response to a user's help request about
> "cache buffer chains", he instructed us to use x$bh in combine with
> dba_extent, we can see which db block is the "hot spot".
>
> And, I run the statspack level5 as you instructed, got a lot of sql,
> but all the Top SQL (disk read or buffer gets) seems to respond fairly
> quickly(<20 sec).
>
> But if I do
>
> SQL> select count(*) from v$sql where executions < 2;
>
> COUNT(*)
> ----------
> 7868
>
> SQL> select count(*) from v$sql ;
>
> COUNT(*)
> ----------
> 11786
>
> I can not attempt to think setting the cursor_sharing=force will help.

And from v$ses_event, when I sort by timed_out column, the top 10 are "latch free". Received on Thu Dec 14 2006 - 12:35:06 CST