RE: cursor: pin S wait on X

Thanks. How would I do all of that without logging in via sqlplus? =) For some strange reason, we can get in with odbc and 3rd party tools.

Wait, never mind. We decided to bounce the database after several cascading problems caught up with us (sql recursive errors, ora-604, max processes reached, etc). We have filed a case with Oracle. If anyone is interested, I can update this thread after we look at the mess we created. =)

-----Original Message-----

From: K Gopalakrishnan [mailto:kaygopal_at_gmail.com] Sent: Friday, April 28, 2006 1:40 PM
To: Schultz, Charles
Cc: Ray Stell; oracle-l
Subject: Re: cursor: pin S wait on X

Charles:

Cursor: pin S wait on X is used like a replacement to library cache pin either during compiling the child or the execution of the KGL object. You see this wait when the mutex is held by the other session on X mode.

You can look the V$mutex_sleep views to find out the requesting session and blocking session and deal this issue like the same old library cache pin waits.

If you want the traditional library cache mechanism to be used for library cahce operations, you can turn this feature (!) off by setting the parameter _use_kks_mutex_pin to false. Other alternative is to look in the mutex_sleep view and find the locations of the waits. This will give a clear picture on which location it is waiting for that wait.

--

Best Regards,
K Gopalakrishnan
Co-Author: Oracle Wait Interface, Oracle Press 2004 http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
--

http://www.freelists.org/webpage/oracle-l Received on Fri Apr 28 2006 - 14:28:08 CDT