Run your test case, and check the contents
of v$open_cursor. Unless my memory has
got it backwards, 
    the pl/sql cursor cache is counted towards 
    max_open_cursors, but the cursors that have
    been held open by the 'dirty tricks department'
    are closed as required if the limit is reached:
    (so should not be responsible for ORA-01000 
    anyway).

    cursors held open as session_cache'd cursors
    are counted independently of max_open_cursors -
    so should not cause an ORA-01000


Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person 
  who can answer the questions, but the 
  person who can question the answers -- T. Schick Jr


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


----- Original Message ----- 
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, December 11, 2003 2:09 PM


> It might be held in the cursor cache, it may even be 
> held in session cursors cache but it will not be counted
> as an open cursor. My suggestion had diagnostic purpose only.
> The problem is, probably, with the tool which explicitly closes 
> cursors too frequently and insufficiently sized shared pool
> which throws cursors out soon after they're closed.
> 
> 
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jonathan Lewis
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).

Reply via email to