We have been doing application load testing lately and I found enq TX index contention being the top contender among other waits. The table with 5 indexes, all it's index columns gets updated via an update for every id in that table by no. of concurrent users defined by the load testing scripts. 10046 trace had lot's of similar lines with varrying p2 and p3 values. WAIT #1: nam='enq: TX - index contention' ela= 3001942 p1=1415053316 p2=65547 p3=816 How can i overcome this wait without amending application behavior. Is this caused by index splits ? Thanks Stalin 10g(10.1.0.3)/solaris -- //www.freelists.org/webpage/oracle-l