Sessions/connections gets hang during update and select operations.

Question

A table with 3 million records, which has customer details data.
Everyday application is executing select and update queries on that table.
Sessions/connections gets hang during update and select operations.
After checking ADDM report, following are the findings:
Please suggest the solutions
Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 145.22 active sessions, 99.77% of total activity.
SQL statements were found waiting for row lock waits.
Recommendation 1: Application Analysis
Estimated benefit is 145.22 active sessions, 99.77% of total activity.
Action
Significant row contention was detected in the TABLE
"AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
row contention in the application logic using the given blocked SQL.
Related Object
Database object with ID 82155.
Rationale
The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The session with ID 50 and serial number 34525 in instance number 1 was
the blocking session responsible for 100% of this recommendation's
benefit.
Symptoms That Led to the Finding:
Wait class "Application" was consuming significant database time.
Impact is 145.22 active sessions, 99.77% of total activity.
Finding 2: Top SQL Statements
Impact is 46.39 active sessions, 31.87% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
Recommendation 1: SQL Tuning
Estimated benefit is 46.39 active sessions, 31.87% of total activity.
Action
Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "974vg65j29pmv" was executed 212 times and had
an average elapsed time of 2494 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "974vg65j29pmv".

Answer 1

**addm report **
          ADDM Report for Task 'TASK_7526'
Analysis Period
AWR snapshot range from 5003 to 5004.
Time period starts at 08-JUL-13 11.00.27 AM
Time period ends at 08-JUL-13 12.00.45 PM
Analysis Target
Database 'AVAYADB' with DB ID 2878789264.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance avayadb, numbered 1 and hosted at
NG-LA04AVAYA01.
Activity During the Analysis Period
Total database time was 563062 seconds.
The average number of active sessions was 155.63.
Summary of Findings
   Description         Active Sessions      Recommendations
                       Percent of Activity
1  Row Lock Waits      155.44 | 99.88       1
2  Top SQL Statements  26.67 | 17.14        1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 155.4 active sessions, 99.88% of total activity.
SQL statements were found waiting for row lock waits.
   Recommendation 1: Application Analysis
   Estimated benefit is 155.44 active sessions, 99.88% of total activity.
   Action
      Significant row contention was detected in the TABLE
      "AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
      row contention in the application logic using the given blocked SQL.
      Related Object
         Database object with ID 82155.
   Rationale
      The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE  ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The session with ID 167 and serial number 6084 in instance number 1 was
      the blocking session responsible for 100% of this recommendation's
      benefit.
   Symptoms That Led to the Finding:
      Wait class "Application" was consuming significant database time.
      Impact is 155.45 active sessions, 99.88% of total activity.
Finding 2: Top SQL Statements
Impact is 26.66 active sessions, 17.14% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
   Recommendation 1: SQL Tuning
   Estimated benefit is 26.67 active sessions, 17.14% of total activity.
   Action
      Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
      possible performance improvements. You can supplement the information
      given here with an ASH report for this SQL_ID.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE  ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The SQL spent only 0% of its database time on CPU, I/O and Cluster
      waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
      Look at performance data for the SQL to find potential improvements.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "974vg65j29pmv" was executed 707 times and had
      an average elapsed time of 794 seconds.
   Rationale
      Waiting for event "enq: TX - row lock contention" in wait class
      "Application" accounted for 100% of the database time spent in
      processing the SQL statement with SQL_ID "974vg65j29pmv".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Additional Information
Miscellaneous Information
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.