關於enq: TX - allocate ITL entry等待事件
SQL> create table trans_test(id number,name varchar2(100)) initrans 1 maxtrans 1;
Table created
SQL> select ini_trans,max_trans,table_name from user_tables a where a.table_name='TRANS_TEST';
INI_TRANS MAX_TRANS TABLE_NAME
---------- ---------- ------------------------------
1 255 TRANS_TEST
In earlier releases, the MAXTRANS parameter determined the maximum number of concurrent update transactions allowed for each data block in the segment. This parameter has been deprecated. Oracle now automatically allows up to 255 concurrent update transactions for any data block, depending on the available space in the block.
Existing objects for which a value of MAXTRANS has already been set retain that setting. However, if you attempt to change the value for MAXTRANS, Oracle ignores the new specification and substitutes the value 255 without returning an error.
對於ini_trans, max_trans的預設值,表級為1,索引級為2. 一般來說不需要做特別的設定。可以根據業務的需要來配置。
以下設定可供參考:
對於大表,資料千萬級以上的表,initrans建議設定為8~16
對於中級表,資料量在百萬到千萬級,initrans建議設定為4~8
對於普通的表,initrans建議設定為1~4
對於此等待事件,解決思路有三種:
1) Depending on the number of transactions in the table we need to alter the value of INITRANS.
If the issue is not resolved by increasing INITRANS then try increasing PCTFREE. Increasing PCTFREE holds more
1) Spreading rows into more number of blocks will also helps to reduce this wait event.
2) Then re-organize the table using move (alter table service_T move;)
3) Rebuild index
Increase INITRANS
here it has been changed to 50:
2) Then re-organize the table using move (alter table move;)
3) Then rebuild all the indexes of this table as below
Increase PCTFREE
space back and so spreads the same number of rows over more blocks. This means that there are more ITL slots
available overall :
A Combination of increasing both INITRANS and PCTFREE
1) Set INITRANS to 50 pct_free to 40
2) Re-organize the table using move (alter table move;)
3) Then rebuild all the indexes of the table as below
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/21374452/viewspace-2157353/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- enq: TX - allocate ITL entry等待事件分析ENQ事件
- [20231026]enq TX - allocate ITL entry的測試4.txtENQ
- 等待事件enq: TX - row lock contention事件ENQ
- 故障排除 | enq:TX - index contention等待事件ENQIndex事件
- Oracle等待事件之enq: TM – contentionOracle事件ENQ
- oracle等待事件之enq: CF – contentionOracle事件ENQ
- [20220518]enq FU - contention等待事件.txtENQ事件
- enq: TX - row lock contentionENQ
- oracle 11.2.0.4 rac叢集等待事件enq: TM - contentionOracle事件ENQ
- 奇異的enq: TX - row lock contentionENQ
- enq: TX - index contention基礎理論ENQIndex
- RAC中的enq: TS等待ENQ
- [20201204]關於等待事件Log File Sync.txt事件
- Oracle Enqueues Wait Events 三 enq: TX - row lock contentionOracleENQAI
- enq: TX - index contention故障修復一例ENQIndex
- Solidity事件,等待事件Solid事件
- 【TUNE_ORACLE】等待事件之等待事件類別Oracle事件
- 基於等待事件的效能診斷(轉)事件
- 故障處理】佇列等待之enq: US - contention案例佇列ENQ
- 【故障處理】佇列等待之enq: US - contention案例佇列ENQ
- Selenium等待事件Waits事件AI
- read by other session等待事件Session事件
- log file sync等待事件事件
- ORACLE 常見等待事件Oracle事件
- latch等待事件彙總事件
- Latch free等待事件(轉)事件
- gc cr request等待事件GC事件
- 【等待事件】library cache pin事件
- 【等待事件】log file sync事件
- 關閉tomcat報錯Cannot allocate memoryTomcat
- 【TUNE_ORACLE】等待事件之日誌等待“log file sync”Oracle事件
- 【TUNE_ORACLE】等待事件之IO等待“read by other session”Oracle事件Session
- 【TUNE_ORACLE】等待事件之IO等待“direct path read”Oracle事件
- 【TUNE_ORACLE】等待事件之IO等待“direct path write”Oracle事件
- Latch free等待事件四(轉)事件
- Latch free等待事件三(轉)事件
- db file scattered read等待事件事件
- db file sequential read等待事件事件