Re: Help me read my statspack report

From: <emdproduction_at_hotmail.com>
Date: 14 Dec 2006 01:24:07 -0800
Message-ID: <1166088247.249368.171390@f1g2000cwa.googlegroups.com>

> You are starving the CPU (see top 5 events, always start there), by
> issuing way too much sorts (see 'sort (rows)'), too many chained rows
> (see 'table fetch continued row') and way way too much full table scans
> (see 'tablescans (short tables)' and 'tablescans (long tables)'
> You must have inefficient and untuned sql. You can track down the SQL
> starving your system, by running statspack(5).
>
> --
> Sybrand Bakker

Thanks. But I think we had too much index scan as well, did you see we have a high logical reads?

Also, could you comment on

        Execute to Parse %:   76.61         Latch Hit %:     99.49
Parse CPU to Parse Elapsd %:   97.32     % Non-Parse CPU:     92.36

 Shared Pool Statistics        Begin   End
                               ------  ------
             Memory Usage %:   94.04   94.02

% SQL with executions>1: 28.31 26.99 % Memory for SQL w/exec>1: 26.11 25.70

Does it mean bind variable is not used here? Received on Thu Dec 14 2006 - 03:24:07 CST