返回顶部
首页 > 资讯 > 数据库 >Trouble shooting for Pin S wait on X
  • 268
分享到

Trouble shooting for Pin S wait on X

2024-04-02 19:04:59 268人浏览 安东尼
摘要

Pin S wait on X is usually due to high parses.  So check for high parsing sqls or tune application

Pin S wait on X is usually due to high parses.  So check for high parsing sqls or tune application to share cursors.  For further diagnosis, please review following note :Note:1349387.1  Trouble shooting 'Cursor: Pin S wait on X' wait
通常是由于高分析。 所以检查高解析sqls或调整应用程序共享游标。 如需进一步诊断,请查看以下注意事项Note:1349387.1  Trouble shooting 'Cursor: Pin S wait on X' wait

What causes 'Cursor: pin S wait on X' waits?

   * Firstly, ensure that the shared pool is sized correctly.
    If the shared pool is under sized or under load generally, this may manifest itself as 'Cursor: pin S wait on X'. If Automatic Memory Management is being used then this should not normally be an issue. See:
    Document 443746.1 Automatic Memory Management (AMM) on 11g
     
    *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

    *Parse Errors, as following note indicates:
Document 1353015.1 How to Identify Hard Parse Failures


solution:
select p2raw from v$session where event = 'cursor: pin S wait on X';

select p2raw,
       to_number(substr(to_char(rawtohex(p2raw)), 1, 8), 'XXXXXXXX') sid
  from v$session
 where event = 'cursor: pin S wait on X';
     
select sid,
       serial#,
       sql_ID,
       STATUS,
       STATE,
       BLOCKING_SESSioN,
       BLOCKING_SESSION_STATUS,
       EVENT
  from v$session
 where SID = &sid;


     
As a result of Bug 7568642 BLOCKING_SESSION EMPTY FOR "CURSOR: PIN S WAIT ON X"  the blocking_session is not populated in 10.2.The bug is fixed in 11g R1.
由于错误7568642 BLOCKING_SESSION为空当等待事件为"CURSOR:PIN S WAIT ON X",blocking_session未在10.2中填充。错误在11g R1中修复

In 11g and 12g, the blocking session can be found directly using the following sql:   
在11g和12g中,可以使用下面的sql直接找到阻塞会话

select sid,
       serial#,
       SQL_ID,
       BLOCKING_SESSION,
       BLOCKING_SESSION_STATUS,
       EVENT
  from v$session
 where event = 'cursor: pin S wait on X';

您可能感兴趣的文档:

--结束END--

本文标题: Trouble shooting for Pin S wait on X

本文链接: https://lsjlt.com/news/46407.html(转载时请注明来源链接)

有问题或投稿请发送至: 邮箱/279061341@qq.com    QQ/279061341

猜你喜欢
  • Trouble shooting for Pin S wait on X
    Pin S wait on X is usually due to high parses.  So check for high parsing sqls or tune application...
    99+
    2024-04-02
  • cursor pin S wait on X
    cursor pin S wait on X 1.等待事件说明 1.1 等待事件说明 A cursor wait is associated with parsing in some form. A se...
    99+
    2024-04-02
  • cursor: pin S && cursor: pin S wait on X
    1.cursor: pin S (1). 发生原因   相同SQL大量并发导致产生该等待事件 (2).措施: 分散mutex争用 select * from du...
    99+
    2024-04-02
  • cursor: pin S wait on X数据库缓慢
    应用反应说系统慢,时间不固定,现象不知道,就是慢。无奈只好登陆系统查查看了。查看系统上现有的快照信息SQL> col mintime for a30SQL> col maxtime for a3...
    99+
    2024-04-02
  • cursor:pin S wait on X故障诊分析
      1.    故障概述      7:15,二节点出现大量的“cursor: pin S wait on X”等待事件,数据库性能下降,持续到7:19分恢复正常,持续时间4分钟左右。 下面是详细的故障分析诊断过程。 2.    故障分析 ...
    99+
    2023-09-23
    数据库 sql mysql
软考高级职称资格查询
编程网,编程工程师的家园,是目前国内优秀的开源技术社区之一,形成了由开源软件库、代码分享、资讯、协作翻译、讨论区和博客等几大频道内容,为IT开发者提供了一个发现、使用、并交流开源技术的平台。
  • 官方手机版

  • 微信公众号

  • 商务合作