Re: distribution of the sleeps on the library cache latches

yes, you're absolutely right. I've inhereted that system. The
shared_pool_size = 750M. I believe it's HUGE and oversized. The application
code is mostly based on literal SQL. The miss rate on the shared pool is
normally about 15%-20% with periodical peaks up to 50%. But the previous DBA
insist that we shouldn't decrease the size of shared pool as the miss rate
will be much higher. He also setup periodical flushing every 3 hours (I
assume he did it in order to prevent ORA-4031).
If I undestand the things right, deacresing of shared_pool_size will
decrease load on shared pool latch _but_ contention on the library latches
will be higher because of higher parse rate. Is it correct and what's your
advice in my case?

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Edward Shevtsov
INET: ed_at_mb.ru
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).