- 最后登录
- 2015-3-25
- 在线时间
- 37 小时
- 威望
- 42
- 金钱
- 391
- 注册时间
- 2012-2-14
- 阅读权限
- 10
- 帖子
- 68
- 精华
- 0
- 积分
- 42
- UID
- 222
|
2#
发表于 2012-3-22 17:30:30
应该是最上面那个SQL被异常hang住了,看样子像个JOB。
What is a 'Cursor: pin S wait on X' wait?A cursor wait is associated with parsing in some form. A session may wait for this event when it is trying to get a mutex pin in Share mode but another session is holding the mutex pin on the same cursor object in exclusive. Frequently, waits for 'Cursor: pin S wait on X' is a symptom and not the cause. There may be underlying tuning requirements or known issues.
What causes 'Cursor: pin S wait on X' waits?- Frequent Hard Parses
If the frequency of Hard Parsing is extremely high, then contention can occur on this pin. - High Version Counts
When Version counts become excessive, a long chain of versions needs to be examined and this can lead to contention on this event - Known bugs
select w.SID "Waiter",
to_number(substr(to_char(rawtohex(p2raw)),
1,
case
when (select instr(platform_name, '64') from DBA_REGISTRY_DATABASE) > 0 then
8
else
4
end),
'XXXXXXXX') "Blocker"
from v$session_wait w
where w.EVENT = 'cursor: pin S wait on X';
[ 本帖最后由 teapot 于 2012-3-22 17:39 编辑 ] |
|