enq: SQ - contention" waits in RAC
SQL> l
1* select name, parameter1, parameter2, parameter3 from v$event_name where name like '&event'
SQL> /
Enter value for event: enq: SQ - contention
old 1: select name, parameter1, parameter2, parameter3 from v$event_name where name like '&event'
new 1: select name, parameter1, parameter2, parameter3 from v$event_name where name like 'enq: SQ - contention'
NAME PARAMETER1 PARAMETER2 PARAMETER3
------------------------------ --------------- --------------- ---------------
enq: SQ - contention name|mode object # 0
SQL>
原因:
最常見的原因是一個或多個序列被大量使用,並且這些序列的快取記憶體大小可能不足以滿足RAC
THe most common cause is that one or more sequences are getting used heavily, and the cache size for those sequences may not be adequate for RAC
解決:
1) Find out the sequence that is causing the "enq: SQ - contention" either from the system state dump, hang analyze output, AWR, or ASH report.
從系統狀態轉儲,掛起分析輸出,AWR或ASH報告中查詢引起"enq:SQ - 爭用"的序列。
2) Issue "show sequence <sequence name>" or "SELECT SEQUENCE_NAME, CACHE_SIZE, ORDER_FLAG FROM USER_SEQUENCES;" after connecting to the problem database
3) If the sequence is NOT defined with CACHE and NOORDER option, the check if the attribute for the problem sequence can be changed to CACHE and NOORDER option.
If the application requires that the problem sequence must NOT be defined using CACHE and NOORDER option, then work with the application development to minimize the use of that sequence.
如果序列沒有用CACHE和NOORDER選項定義,則檢查問題序列的屬性是否可以更改為CACHE和NOORDER選項。
如果應用程式要求不能使用CACHE和NOORDER選項來定義問題序列,那麼應用程式開發將最小化該序列的使用。
4) If the sequence is defined with CACHE and NOORDER option and if the cache size is 20, the default cache size, (or a small value like 100), increase the cache size to 10000 by issuing
如果使用CACHE和NOORDER選項定義了序列,並且如果快取記憶體大小為20,則預設快取記憶體大小(或像100這樣的小數值)透過發出將快取記憶體大小增加到10000
ALTER SEQUENCE <cache name> CACHE 10000;
1* select name, parameter1, parameter2, parameter3 from v$event_name where name like '&event'
SQL> /
Enter value for event: enq: SQ - contention
old 1: select name, parameter1, parameter2, parameter3 from v$event_name where name like '&event'
new 1: select name, parameter1, parameter2, parameter3 from v$event_name where name like 'enq: SQ - contention'
NAME PARAMETER1 PARAMETER2 PARAMETER3
------------------------------ --------------- --------------- ---------------
enq: SQ - contention name|mode object # 0
SQL>
原因:
最常見的原因是一個或多個序列被大量使用,並且這些序列的快取記憶體大小可能不足以滿足RAC
THe most common cause is that one or more sequences are getting used heavily, and the cache size for those sequences may not be adequate for RAC
解決:
1) Find out the sequence that is causing the "enq: SQ - contention" either from the system state dump, hang analyze output, AWR, or ASH report.
從系統狀態轉儲,掛起分析輸出,AWR或ASH報告中查詢引起"enq:SQ - 爭用"的序列。
2) Issue "show sequence <sequence name>" or "SELECT SEQUENCE_NAME, CACHE_SIZE, ORDER_FLAG FROM USER_SEQUENCES;" after connecting to the problem database
3) If the sequence is NOT defined with CACHE and NOORDER option, the check if the attribute for the problem sequence can be changed to CACHE and NOORDER option.
If the application requires that the problem sequence must NOT be defined using CACHE and NOORDER option, then work with the application development to minimize the use of that sequence.
如果序列沒有用CACHE和NOORDER選項定義,則檢查問題序列的屬性是否可以更改為CACHE和NOORDER選項。
如果應用程式要求不能使用CACHE和NOORDER選項來定義問題序列,那麼應用程式開發將最小化該序列的使用。
4) If the sequence is defined with CACHE and NOORDER option and if the cache size is 20, the default cache size, (or a small value like 100), increase the cache size to 10000 by issuing
如果使用CACHE和NOORDER選項定義了序列,並且如果快取記憶體大小為20,則預設快取記憶體大小(或像100這樣的小數值)透過發出將快取記憶體大小增加到10000
ALTER SEQUENCE <cache name> CACHE 10000;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31397003/viewspace-2149628/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 'enq: TX - index contention' Waits in a RAC Environment. [ID 873243.1]ENQIndexAI
- enq:SQ-contention / DFS lock handle(SV)ENQ
- 【效能調整】等待事件 enq: SQ - contention事件ENQ
- enq: SQ - contention 等待事件處理辦法ENQ事件
- Troubleshooting 'enq: TX - index contention' WaitsENQIndexAI
- 【MOS】Troubleshooting 'enq: TX - index contention' Waits (文件 ID 873243.1)ENQIndexAI
- Oracle優化案例-系統切換引起的enq: SQ - contention(二十八)Oracle優化ENQ
- enq: US - contentionENQ
- enq: HW - contentionENQ
- enq: TM - contentionENQ
- enq:TM contentionENQ
- enq: DX - contentionENQ
- enq: TS - contentionENQ
- oracle 11.2.0.4 rac叢集等待事件enq: TM - contentionOracle事件ENQ
- zt_Oracle enq: TX contention 和 enq: TM contention 等待事件OracleENQ事件
- enq:TX - index contentionENQIndex
- enq: TX - index contentionENQIndex
- enq: TX - row lock contentionENQ
- 關於enq: US – contentionENQ
- enq: WF - contention等待事件ENQ事件
- enq: CF - contention 等待事件ENQ事件
- enq: TX - index contention等待ENQIndex
- enq: TS - contention 等待事件ENQ事件
- 【MOS】12c RAC "enq: IV - contention" (文件 ID 2028503.1)ENQ
- 等待事件之enq: HW - contention事件ENQ
- 【故障解決】enq: PS - contentionENQ
- enq:TM-contention事件等待ENQ事件
- 消除 enq: DX - contention 等待事件ENQ事件
- Oracle等待事件之enq: TM – contentionOracle事件ENQ
- 等待事件enq: TX - row lock contention事件ENQ
- oracle等待事件之enq: CF – contentionOracle事件ENQ
- 【等待事件】-enq: TX - row lock contention事件ENQ
- Metlink:Performance issues with enq: US - contentionORMENQ
- [20200120]oracle wait event "enq: SQ – contention" and DBA_DB_LINK_SOURCES.txtOracleAIENQ
- 關於12C RAC 上的top5 問題:enq: IV - contentionENQ
- enq: TX - index contention基礎理論ENQIndex
- 故障排除 | enq:TX - index contention等待事件ENQIndex事件
- 奇異的enq: TX - row lock contentionENQ