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 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';
通常是由於高分析。 所以檢查高解析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';
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31397003/viewspace-2149609/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- cursor pin S wait on XAI
- cursor: pin S wait on XAI
- cursor:pin S wait on XAI
- Cursor pin S wait on X 事件AI事件
- cursor: pin S wait on X模擬AI
- cursor: pin S wait on X等待事件。AI事件
- cursor:pin S wait on X故障診分析AI
- oracle等待事件之cursor:pin S wait on XOracle事件AI
- cursor: pin S wait on X等待實驗二AI
- cursor: pin S wait on X等待事件模擬AI事件
- trouble shooting案例分享
- cursor: pin S wait on X等待事件模擬(轉)AI事件
- library cache lock和cursor: pin S wait on X等待AI
- AWR報告實戰之cursor:pin S wait on XAI
- zt_小荷_記得cursor pin s wait on xAI
- 【故障】cursor: pin S wait on X等待事件大量出現AI事件
- 記一次cursor pin s wait on X的處理AI
- cursor: pin S wait on X等待事件的處理過程AI事件
- 一次cursor: pin S wait on X事件的跟蹤AI事件
- ORA-27102 O/S ERROR: (OS 1445)..... trouble shootingError
- DNS查詢 and trouble-shooting caseDNS
- Trouble shooting latch: cache buffers chainsAI
- [20170707]cursor: pin S wait on X(10G)AI
- latch: row cache objects 和cursor: pin S wait on X共同出現ObjectAI
- 【徵文】cursor: pin S wait on X等待事件的處理過程AI事件
- 【新炬網路名師大講堂】cursor: pin S wait on X模擬AI
- aix login shell permission error trouble shooting.AIError
- [20180301]模擬cursor pin S wait on X.txtAI
- 分散式引起的cursor: pin S wait on X 事件一次問題處理分散式AI事件
- 解決RAC節點因cursor: pin S wait on X無法登陸案例一則AI
- sql version count引發cursor:pin s wait x及library cache latch library cache lockSQLAI
- Disk arrary's adapter in troubleAPT
- “舉報”阿里巴巴 Arthas,大幅降低 OOM Trouble shooting 門檻阿里OOM
- Trouble shooting(問題解決):centos 7 gnome show someting has gone wrong.CentOSGo
- Qt 在window mobile 開發環境安裝配置及一些Trouble ShootingQT開發環境
- DB Issue Trouble Shooting Guideline (資料庫問題處理指導)GUIIDE資料庫
- 等待事件Cursor: Pin S Wait On X和Library Cache Load Locks可能意味著過度的記憶體調整事件AI記憶體
- cursor: pin S 等待事件事件