Investigating EBS Row Lock Contention

You should primarily use the DBA Blocking Sessions report, which shows the chain of currently blocking and blocked database sessions derived from `v$wait_chains`. This gives you the current lock scenario.

For analysis involving the Active Session History (ASH), utilize the DBA SGA Blocking Session Summary. While row lock scenarios sometimes involve idle blocking sessions not visible in ASH, this summary helps correlate active blocking events. You can perform further analysis using a pivot in Excel for faster root cause identification.

The DBA AWR SQL Performance Summary report provides visibility into ‘Application Wait Time’, which captures total elapsed time in seconds from the wait event class ‘Application’, such as ‘enq: TX – row lock contention’ caused by an uncommitted session’s update blocking another session.