Re: [External] : Re: Open cursor error
Date: Thu, 24 Aug 2023 09:38:59 +0100
Message-ID: <CAGtsp8kWs7wMUtU9qSj79MGScFWtbseaM8=09DD9Dh_u9zg-qA_at_mail.gmail.com>
The "guilty" cursor_type being "OPEN" is what I wanted to see - if it had
been one of the internal types then you might have have uncovered an Oracle
bug, but simply "OPEN" means it's almost certainly an application coding
error of the type that Andy described. (viz: exceptions being raised and
cursors not being closed in the handler - e.g. when others then null;
another is the server-side code explicitly opening a cursor and passing the
cursor handle to the client-side and the client forgetting to close.)
Pick a couple of sessions with a large number of cursors of type OPEN, and
aggregate the SQL_ID - the results may be interesting, then check username
and sql_text. This may tell you almost everything you need to know about
where the error is coming from.
Regards
Jonathan Lewis
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Aug 24 2023 - 10:38:59 CEST