enq: TX - row lock contention and UPDATE
Hi,
We have an application and in AWR we see the next wait event:
The transaction generates this wait event is the next one:
update seg_usuarios set num_intentos=:1 where username=:2
It runs 41 times in the AWR, but each user of application executes this update with his username, then we don´t understand why this sentence can locks and produce a lot of waits.
Can you explain us?
Thanks.
Laura.
We have an application and in AWR we see the next wait event:
|
Event |
Waits |
Time(s) |
Avg Wait(ms) |
% Total Call Time |
Wait Class |
|
enq: TX - row lock contention |
38341 |
16907 |
441 |
65.6 |
Application |
The transaction generates this wait event is the next one:
update seg_usuarios set num_intentos=:1 where username=:2
It runs 41 times in the AWR, but each user of application executes this update with his username, then we don´t understand why this sentence can locks and produce a lot of waits.
Can you explain us?
Thanks.
Laura.
0