Path: news.easynews.com!easynews!sjc-peer.news.verio.net!news.verio.net!sn-xit-01!sn-xit-02!supernews.com!postnews1.google.com!not-for-mail From: buckeye234@excite.com (Patrick) Newsgroups: comp.databases.oracle.server Subject: Re: ORA-04031 Errors - Unsharable SQL Date: 10 Oct 2001 09:57:54 -0700 Organization: http://groups.google.com/ Lines: 26 Message-ID: <3bbfc440.0110100857.652bcf27@posting.google.com> References: <3BC3E93C.4C2E0C1F@office.casema.nl> NNTP-Posting-Host: 170.128.174.146 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1002733075 9497 127.0.0.1 (10 Oct 2001 16:57:55 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 10 Oct 2001 16:57:55 GMT Xref: easynews comp.databases.oracle.server:120841 X-Received-Date: Wed, 10 Oct 2001 09:57:39 MST (news.easynews.com) I did look at that bug on MetaLink. The error message caused by that bug is the same as I am seeing, but the underlying symptoms are different. The bug causes permanent memory to grow while free memory decreases, in my case permanent memory is stagnant. Only the sql_area memory usage grows. I am able to reclaim free memory by flushing the shared pool, which would not work in the case of the bug (I have automated that by the way, never was doing it manually;). Also, my first action after experiencing the problem and viewing MetaLink, was to set the _db_handles_cached=0 parameter. It did not fix the problem. Based on everyone's response, all I can do for now is what I have been doing and to push the developers to fix their code. I could threaten to put them on the 'Shoot the developers' list.......... Thanks for everyone's feedback. It is much appreciated. later ...... Berno Strik wrote in message news:<3BC3E93C.4C2E0C1F@office.casema.nl>... > Hello Patrick, > > You should also look on metalink at bug 1649372. It describes the same symptoms. > It can be fixed by setting the undocumented parameter: _db_handles_cached=0. > > HTH Berno