Hello guys,
i am facing many "enq: TX - row lock contention" wait events in an AWR report and have a look at the statistic for "Segments by Row Lock Waits" and it looks like this.
Segments by Row Lock Waits
-> % of Capture shows % of row lock waits for each top segment compared
-> with total row lock waits for all segments captured by the Snapshot
Row
Tablespace Subobject Obj. Lock % of
Owner Name Object Name Name Type Waits Capture
---------- ---------- -------------------- ---------- ----- ------------ -------
OPRASC POPRASC RANT~0 INDEX 15,995 4.69
OPRASC POPRASC VFEN TABLE 15,340 4.49
OPRASC POPRASC FJIJJOWMNV~001 INDEX 14,098 4.13
OPRASC POPRASC SEAPOLNMNB~0 INDEX 14,050 4.12
OPRASC POPRASC WESAC~SR3 INDEX 12,976 3.80
-------------------------------------------------------------
Database version: 10.2.0.2
I can understand the statistic for the table VFEN, but why are there so many indexes in that statistic? And what can cause a "Row Lock Wait" on an index segment?
There is no FK or and PK constraint. There are only some constraints on that corresponding table columns for "IS NOT NULL".
Thanks for your help.
Regards
Stefan