Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: increasing open_cursors from 300 to 3000
open_cursor -- how many concurrently opened cursors you can have. session_cached_cursors -- how many cached CLOSED cursors you can have. it is hard to explain a relationship where none really exists... The only relationship they really have is -- they both have cursors at the end of their name.... Consider: ops$tkyte@ORA920> show parameter _cursors NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ open_cursors integer 50 session_cached_cursors integer 100 that means, "you cannot have more then 50 open at the same time - but we might cache 100 of them for you off to the side..."At 09:21 AM Tuesday, Wolfson Larry - lwolfs wrote:
Paula,
I heard after upgrading to 9.2.06 session_cached_cursors replaced open_cursors.
Anybody else hear that?
Larry Wolfson
From: oracle-l-bounce@freelists.org [ mailto:oracle-l-bounce@freelists.org] On Behalf Of Paula_Stankus@doh.state.fl.us
Sent: Monday, October 17, 2005 3:04 PM
To: oracle-l@freelists.org
Subject: RE: increasing open_cursors from 300 to 3000
We are running with about 500 concurrent users.
O racle Version 9.2.0.6
Solaris 2.9
0RA-1000 "Too many open cursors" error when selecting from a sequence over a dblink.
Metalink Note:238407.1 describes the error and indicates that the bug id is corrected in 9.2.0.3 and later. We're running 9.2.0.6.
A nyone have any advice or head's up when increasing open_cursors significantly. I would think that if these open cursors are used then there might be memory issues.
************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. **************************************************************************