Re: need help on statspack report, Parse CPU to Parse Elapsd %

"VC" <boston103_at_hotmail.com> wrote in message news:Jqq2c.129022$4o.167197_at_attbi_s52...
> Hello Joe,
>
> "Joe" <yung103_at_netvigator.com> wrote in message
> news:c2co7r$nk31959_at_imsp212.netvigator.com...
> > Hi Oracle Experts,
> >
> > Attached please find the statspack report I generated on 04-MAR-2004.
> > We are running Oracle eBuisness Suite on AIX.
> A cursory look at you statspack shows:
>
> 1. High enqueue wait time. The usual cause is that several sessions are
> trying to lock the same row (SELECT FOR UPDATE probably?) and the average
> wait time is 3 seconds per enqueue. Other reasons may be bitmap indexes
> update/unindexed foreign keys/lack of ITL slots, in the order of
decreasing
> probability.
>
> 2. The second highest event, latching, is probably caused by some SQLs not
> using bind variables (library cache latching).
>
> 3. The percentage of rollbacks is quite high: 7.24%
>
> 4. The CPU used by the session is below waits for enqueue/latches
(1,509,296
> cs).
>
> 5. You probably have an 8-cpu machine.
>
> Val
>
>

how do you know that isnt perfectly normal in his system?

need somethint to compare against otherwuse you are just guessing and probbaly leading the OP up the garden path Received on Sat Mar 06 2004 - 15:31:01 CST