Initrans vs tx-row lock contention
608007Sep 23 2008 — edited Sep 24 2008Hello All,
I'm a novice to performance tuning and I'm faced with TX- row lock contention on 1 particular table.
From my understanding, when using automatic segment management then the TRANSACTION slots are automatically increased and decreased by Oracle as it needs.
On the other hand, the INITRANS on a table suggests the amount of guaranteed slots available on the table at startup time.
My first question, is can TX-row lock contention be caused by a lack on INITRANS. My second question, is how to see the amount of slots available on the table versus the amount of transactions waiting for a slot.
I know that, when I do a AWR report, I can see if there are any ITL waits, but is this a concrete answer to my question?
Should I be looking at this problem from a totally different angle?
Regards
Jan S.