Bug 5907779

最新推荐文章于 2024-10-18 13:02:57 发布

coo3678

最新推荐文章于 2024-10-18 13:02:57 发布

阅读量118

点赞数

文章标签：数据库

今天早上数据库巡检发现cpu 100%，客户随后通知业务系统比较慢，

输入如下命令：发现大量等待事件

select sid,seq#,event from v$session_wait where wait_class <> 'Idle';
SID       SEQ#    EVENT
---------- ---------- ----------------------------------------------------------------
   3219    13646 cursor: pin S wait on X
   2932    38752 cursor: pin S wait on X
   2939    30790 cursor: pin S wait on X
   3025    13249 cursor: pin S wait on X
   3051    34571 cursor: pin S wait on X
   3059    32406 cursor: pin S wait on X
   3115    24301 cursor: pin S wait on X
   3175    42869 cursor: pin S wait on X
   3164    4197 cursor: pin S wait on X
   3159    20237 cursor: pin S wait on X
执行如下命令

alter system set cursor_sharing=force;

等待事件消失.

10203 rac

查到一个bug

Subject:  Bug 5907779 - Self deadlock hang on "cursor: pin S wait on X" (typically from DBMS_STATS)
  Doc ID:  5907779.8 Type:  PATCH
  Modified Date :  03-APR-2009 Status:  PUBLISHED

Bug 5907779  Self deadlock hang on "cursor: pin S wait on X" (typically from DBMS_STATS)
This note gives a brief overview of bug 5907779.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.
This bug is marked as an important issue.

Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions >= 10.2.0.3 but < 10.2.0.4
Versions confirmed as being affected 10.2.0.3

Platforms affected Generic (all / most platforms affected)

It is believed to be a regression in default behaviour thus:
Regression introduced in 10.2.0.3

Fixed:
This issue is fixed in 10.2.0.3 Patch 6 on Windows Platforms
10.2.0.4 (Server Patch Set)

Symptoms: Related To:
Deadlock
Hang (Process Hang)
Waits for "cursor: pin S wait on X"
(None Specified)
DBMS_STATS

Description
This problem is introduced in 10.2.0.3
A process may hang with a self deadlock typically when executing
DBMS_STATS. The hung process shows itself waiting on a
"cursor: pin S wait on X" waitevent waiting for an object
that it has pinned itself.

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.

References
Bug 5907779 (This link will only work for PUBLISHED bugs)
Note 245840.1 Information on the sections in this article