old open cursor entries

  • From: Patrice sur GMail <patrice.boivin@xxxxxxxxx>
  • To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 14 Jun 2012 14:16:33 -0300

We are seeing in EM11g lists of old cursors for user sessions, some with
locks.  Some sessions can have over twenty entries in the open cursors page
even if their last statement is a simple select statement.
As if there is old shadow SQL or zombie cursor locks left in the database
server side even though the SQL was run a week or up to a month ago.

Normally for cursors it stores the info in the shared pool, in case someone
submits the same SQL again later.  It may store the compiled code too I
think but whether that's true or not, wouldn't locks be released once the
user finishes using the cursor?

These are not the 11g row exclusive locks related to foreign keys, the SQL
we see includes select and insert statements, as well as recursive SQL like
inserts into the sys.aud$ table.

-- Patrice

[image: Facebook]
<http://www.facebook.com/profile.php?id=100000206805521> [image:
LinkedIn] <http://ca.linkedin.com/pub/patrice-boivin/a/933/5a9> [image:
Twitter] <http://www.twitter.com/PatriceBoivin> [image:
Digg] <http://digg.com/patriceboivin> [image:
  Get a signature like this.


Other related posts:

  • » old open cursor entries - Patrice sur GMail