SR 4 DB

first of all, some lines about theory. interested transaction list (ITL) Information in the block header of every segment that determines whether a transaction was uncommitted when the database began modifying the block. Entries in the ITL describe which transactions have rows locked and which rows in the block contain committed and uncommitted changes. ITL Waits ITL Waits happens when a session sets a DML transaction and this needs to acquire an ITL slot within data header block but there is not enough space in the pctfree area hence the session has to wait that other DML transaction is commited o rolled back therefore an ITL slot will be avaiable. 

I am working in a new post : "Open Cursor Current by program", i hope to finish it next week. thanks for reading.

If we saw "ITL Waits" in the report "Summary of Tablespace" section "Statistics", we can use this procedure to diagnostic and resolve that.  We have used this method  in high transactional environment and it worked very well in order to find problems and resolve. Step 01  - ITL Waits We run this query  to know which segments have more ITL waits.    SELECT  Owner ,          Object_Name ,          Subobject_Name ,  Object_Type,  Value      FROM  V$Segment_Statistics c     WHERE      Tablespace_Name  =   UPPER   ( '&parTABLESPACE' )           AND   Value   >   0           AND  Statistic_Name  =   'ITL waits' ORDER   BY   Value   DESC; Owner        OBJECT_NAME                 SUBOBJECT_NAME      OBJECT_TYPE            VALUE ------------ --------------------------- ------------------- ---------------------  --------- PTP          THIAT_CONCILIACION_AA_1                          TABLE