RE: increasing open_cursors from 300 to 3000

While increasing from 255 to 500 isn't a problem, it isn't the solution is developers aren't closing cursors. It is just giving you a bigger pool to piss in. Some applications open a cursor and reuse it. That is fine. It is applications that open a cursor and leak them that is a problem. Jim

-----Original Message-----

From: oracle-l-bounce_at_freelists.org on behalf of Arul Ramachandran Sent: Fri 10/21/2005 6:05 PM
To: Paula_Stankus_at_doh.state.fl.us; oracle-l_at_freelists.org Subject: Re: increasing open_cursors from 300 to 3000  

Hi Paula,  

In the past with Oracle8i, I've increased OPEN_CURSORS (for ORA-1000) almost doubled from 255 to 500, without any negative side effects, as a temporary fix when developers rolled out Java code that did not close cursors. This helped us buy more time before we'd hit another ORA-1000, sort of treating the symptom.  

Arul      

On 10/20/05, Prem <premjhere_at_gmail.com> wrote:

        Hi Paula ,         

	As Larry said, starting with release 9.2.0.5, the SESSION_CACHED_CURSORS 
	initialization parameter now determines the upper bound for PL/SQL cursor
	caching instead of OPEN_CURSORS initialization parameter.
	For more info', refer README for patch # 3948480.
	
	Regards,
	Prem Khanna J 
	
	

--

http://www.freelists.org/webpage/oracle-l Received on Fri Oct 21 2005 - 23:14:38 CDT