Re: Spotting the real cause of a Production slowdown (10g)
- From: "Alex Gorbachev" <gorbyx@xxxxxxxxx>
- To: "Schultz, Charles" <sac@xxxxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 09:34:48 +0200
Another point is huge shared pool you mentioned and its resizing
during the problem. I do not trust automatic SGA management in 10g for
critical OLTP systems with high workload. Perhaps, Oracle increases
shared pool and this causes some overhead. If library cache is huge
than more objects are protected by a single child latch. I.e. huge
shared pool can in fact cause the problem.
See if you can correlate shared pool increase BEFORE (or maybe at the
very same moment) the start of the problem. Perhaps, you should
disbale automatic SGA management feature.
2006/4/20, Schultz, Charles <sac@xxxxxxxxxxxxx>:
> That is insightful, thank you.
>
> In light of trying to prove it (so that we can officially point our
> finger and resolve this issue so it does not happen again), it sounds
> like we are going to have to focus on the AWR to see if the workload is
> actually higher or not. Again, hypothetically, if the latch waits are
> merely a nuisance, they make the analysis that much harder because they
> in turn cause some of the cpu load. Is it possible to use AWR and
> attempt to exclude latch waits and their side effects? Perhaps we need
> to concentrate on periods of time before latch waits become an issue?
>
> Again, thanks for this thought. Another direction for us to pursue.
>
--
Best regards,
Alex Gorbachev
--
//www.freelists.org/webpage/oracle-l
Other related posts:
