RE: Obsolete Initialization Parameters

From: Jesse, Rich <Rich.Jesse_at_quadtechworld.com>
Date: Mon, 23 Feb 2004 14:20:44 -0600
Message-ID: <FBE1FCA40ECAD41180400050DA2BC54004E9371D@qtiexch2.qgraph.com>

Is this from Windohs ODBC connections? If so, check to see if checking "Enable closed cursors" on the offending clients will help. I believe it's a coding problem, but this was a viable workaround for a vendor app that bumped into 5000 open cursors between <10 connections.

BTW, we used this to track down our offending user on 8.1.7.4.0:

SELECT voc.sql_text, vs.username, vs.osuser, count(*) FROM v$open_cursor voc, v$session vs
WHERE voc.address = vs.sql_address
GROUP BY voc.sql_text, vs.username, vs.osuser ORDER BY 4 DESC; HTH! GL!
Rich

Rich Jesse                        System/Database Administrator
rich.jesse_at_quadtechworld.com      QuadTech, Sussex, WI USA

-----Original Message-----
> From: David Boyd [mailto:davidb158_at_hotmail.com]
> Sent: Monday, February 23, 2004 1:37 PM
> To: oracle-l_at_freelists.org
> Subject: Obsolete Initialization Parameters
>
>
> Hi List,
>
> We got ORA-1000 errors "Too many open cursors" and our
> open_cursors is set
> to 1000. I was wondering if it's better to increase
> open_cursor or set
> CLOSE_CACHED_OPEN_CURSORS = true to resolve the problem. I know
> CLOSE_CACHED_OPEN_CURSORS is an obsolete initialization
> parameter in Oracle
> release 8.1. If I want to set CLOSE_CACHED_OPEN_CURSORS =
> true, do I have
> to set _close_cached_open_cursors=true? Or is it better to
> ask developer
> using SET_CLOSE_CACHED_OPEN_CURSORS Procedure in the application?

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Mon Feb 23 2004 - 14:20:08 CST