Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: enq: TX - index contention

RE: enq: TX - index contention

From: Hollis, Les <>
Date: Tue, 22 Mar 2005 11:48:10 -0600
Message-ID: <>

Addendum.....this is cut from the Database Fundamentals II training course from Oracle Education....Power Point Slides

INITRANS: Guarantees a minimum level of concurrency. It defaults to 1 for a data segment and 2 for an index segment, guarantees a minimum level of concurrency. For example, if set to 3, INITRANS ensures that at least three transactions can concurrently make changes to the block. If necessary, additional transaction slots can be allocated from the free space in the block to permit more concurrent transactions to modify rows in the block.

True in both the 9.0.1 release documentation AND in the 9.2.0.x Documentation.

-----Original Message-----

From: Hollis, Les=20
Sent: Tuesday, March 22, 2005 11:32 AM
To: ''; Subject: RE: enq: TX - index contention

I think not.

SQL> create table junky1 (name varchar2(5));

Table created.

SQL> select ini_trans from user_tables where table_name =3D 'JUNKY1';



-----Original Message-----

[] On Behalf Of Powell, Mark D Sent: Tuesday, March 22, 2005 10:19 AM
Subject: RE: enq: TX - index contention

I believe that the default number of initrans for a table has been raised to
two as of version 9.0 =20

-----Original Message-----

On Behalf Of K Gopalakrishnan
Sent: Tuesday, March 22, 2005 10:10 AM
Subject: Re: enq: TX - index contention


TX enqueue waits with LMODE 4 can happen for the following reasons. Quoting from 'Oracle Wait Interface'

"A wait for the TX enqueue in mode 4 is normally due to one of the following
ITL (interested transaction list) shortage Unique key enforcement Bitmap index entry

Here, we will talk about the ITL, which is a transaction slot in a data block. The initial number of ITL slots is defined by the INITRANS clause and
is limited by the MAXTRANS clause. By default, a table has 1 ITL and an index has 2 ITLs. Each ITL takes up 24 bytes and contains the
transaction ID in the format of USN.SLOT#.WRAP#. Every DML transaction needs
to acquire its own ITL space within a block before data can be manipulated.
Contention for ITL occurs when all the available ITLs within a block are currently in use and there is not enough space in the PCTFREE area for Oracle to dynamically allocate a new ITL slot. In this case, the session will wait until one of the transactions is committed or rolled back, and it
will reuse that ITL slot. ITL is like a building parking space. Everyone who
drives to the building needs a parking space. If the parking lot is full,
you have to circle the lot until someone leaves the building. "

So I would expect any of the above conditions in your case? You may want to query the V$segment_statistics for ITL waits to eliminate the ITL
issue. If you have bitmap indexes, that should be one of the casues for those excesive waits. The wait time is close to 3 seconds and I suspect that
could be because of the bitmap index issue,

Best Regards,
K Gopalakrishnan
Co-Author: Oracle Wait Interface, Oracle Press 2004


-- Received on Tue Mar 22 2005 - 12:49:29 CST

Original text of this message