RE: TX - row lock contention ... usn<<16 | slot ... sequence Wait

Date: Fri, 18 Jan 2008 10:29:43 +0530
Message-ID: <>


During a Benchmark Run following Wait is extremely High

enq: TX - row lock contention
usn<<16 | slot

Qs How is the issue to be approached / actioned please?

Cheers & Thanks


select * from v$session_wait sw

04:15:31   2  where sw.event not in ('rdbms ipc message','smon timer','pmon timer',
04:15:31   3  'SQL*Net message from client','lock manager wait for remote message',
04:15:31   4  'client message', 'SQL*Net more data from client', 'pipe get',
04:15:31   5  'null event', 'PX Idle Wait', 'single-task message', 'wakeup time manager')
04:15:31   6  order by sw.seconds_in_wait desc;


         10569 38
enq: TX - row lock contention

name|mode                                                            1415053318
usn<<16 | slot                                                        262144022
sequence                                                                    167
00000000000000A7     4217450380              1
Application                                                                   0
           2179 WAITING

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***
Received on Thu Jan 17 2008 - 22:59:43 CST

Original text of this message