Re: cursor: pin S wait on X

10.2 turns on mutexes by default. The short-term workaround is to turn off
mutexes (_kks_use_mutex_pin = FALSE). There are several related bugs,
notably:
5184776 10.2.0.2.0 RDBMS 10.2.0.2.0 PRODID-5 PORTID-23
Abstract: HIGH 'CURSOR: PIN S WAIT ON X'

We had one database that blocked on some dictionary objects, prohibiting all
logins (even as sysdba). Unfortunately, since we were not able to reproduce,
we had to close the case as Oracle wanted a hanganalyze. If you can get more
information from various mutex related views, I strongly advise you open a
case with Oracle.

On 10/6/06, Sanjay Mishra <smishra_97@xxxxxxxxx> wrote: 

I had new Application in 10g Rel2 into production where I am seeing
blocking issue which will severely affect the application as it almost
stopped working and here is what I can see in EM

Session    Session ID .......Wait Class            Wait Event
Blocked
3               111                 Concurrency         cursor:pin S wait
on X
0               113                 Concurrency         Library cache load
lock
0               119                 Concurrency         library cache load
lock
0               133                 Concurrency        Library Cache Load
Lock


I have not set any _mutex variable and it is using default. Any suggestion

TIA
Sanjay

------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone 
Calls<http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>to
 the US (and 30+ countries) for 2¢/min or less.




--
Charles Schultz

Other related posts: