Re: Massive Wait Events "Cursor: pin S wait on X" with PL/SQL in 11.1.0.7

Why do internal function names mean nothing? It's just an information which
can be useful under certain circumstances - like when you search metalink.

Anyway just from curiosity, can you share the result of the
v$mutex_sleep_history view like following?

TPACK@ukja1106> select mutex_type, location from v$mutex_sleep_history

  2  where requesting_session = 125;

MUTEX_TYPE                       LOCATION

-------------------------------- --------------------------------------

Cursor Pin                       kkslce [KKSCHLPIN2]

Cursor Pin                       kkslce [KKSCHLPIN2]



================================
Dion Cho - Oracle Performance Storyteller

http://dioncho.wordpress.com (english)
http://ukja.tistory.com (korean)
http://dioncho.blogspot.com (japanese)
http://ask.ex-em.com (q&a)
================================


2010/5/7 Martin Klier <usn@xxxxxxxxx>
>
> Hi,
>
> Dion Cho schrieb:
> > Querying V$MUTEX_SLEEP_HISTORY view would be another starting point -
> > who is blocking mutex to execute which codes?
>
> thanks for the reply. But to be honest, the LOCATION field does tell me
> nothing - looks like internal function names. How does the information
> help me to find out the culprit?
>
> Thanks in advance
> Martin
>
>
>
> --
> Usn's IT Blog for Linux, Oracle, Asterisk
> http://www.usn-it.de
>

Other related posts: