RE: Latch Contention
- From: Stephen.Lee@xxxxxxxx
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 1 Mar 2004 17:09:50 -0600
Possibly lack of bind variables. Without them, the shared pool gets filled
up with a bunch of doo-doo, then you get waits while Oracle manages all that
doo-doo. If you're just playing around, you could see if reducing the size
of the shared pool helps. It gives Oracle less doo-doo to fuss with.
-----Original Message-----
Today we had problems with latch contention in our production Oracle Apps
database. I saw lots of latch free waits, of the cache buffer chains and
library cache variety. I looked for the most resource intensive sessions.
But nothing stood out. Finally I flushed the shared pool (Cary Millsap is
going to cringe at this time........). That cleared all the latch free waits
and users reported better performance. Didn't want to flush the shared pool
but had to do it due to month end close processing that was getting severly
bogged down. I still haven't found the root cause. My question is where to
look for the root cause next time.
Here are some stats I gathered while the problem occurred.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
