|<< Back to previous view|
[QA-56] "cursor: mutex X" Created: 27/Jul/13 Updated: 28/Jul/13
|Project:||Questions & Answers|
|Type:||Oracle - Database Tuning||Priority:||Major|
|Reporter:||ubTools Support||Assignee:||ubTools Support|
The customer has upgraded from Oracle 10.2.0.5 to Oracle 18.104.22.168.7. They encountered library cache lock problem.
Some excerpt from the AWR:
|Comment by ubTools Support [ 27/Jul/13 10:42 AM ]|
Some excerpt from the HANGANALYZE trace:
There are many other sessions waiting on library cache lock in the trace. And, they are blocked by SID#8008 which is waiting on cursor: mutex X. SID#8008 blocks 426 sessions.
|Comment by ubTools Support [ 27/Jul/13 01:03 PM ]|
Unfortunately, the blocker session SID#8008 exited. But, a new blocker SID#7579 appeared. Some excerpt from its ERRORSTACK LEVEL 3 trace:
Mutex IDN 0xd4d88873 is hold in EXCL mode at mutex address 0x22c1df2c18. The holder SID is 7579. The mutex type is Cursor Parent
Waiting session holds the same mutex IDN in EXCL mode but in the different mutex address and the different mutex type. No other holder encountered in the SYSTEMSTATE trace.
|Comment by ubTools Support [ 28/Jul/13 01:26 PM ]|
Some excerpt from AWR:
The mutex sleep location is kkshhcdel [KKSHBKLOC4]. Nothing found about it in Metalink.
|Comment by ubTools Support [ 28/Jul/13 05:33 PM ]|
Change the SQL text.
|Comment by ubTools Support [ 28/Jul/13 05:36 PM ]|
|The customer will open an SR to Oracle Support. I'll update this issue later with SR result.|