How To Fix DB6118 - Too many lock escalations occur in the system

DB6118 - Overview

• Message type: E = Error

• Message class: DB6 - DB6: Alert Monitoring and Alert Configuration

• Message number: 118

• Message text: Too many lock escalations occur in the system

What causes this issue?

As a transaction is accessing too many records of a table to make
changes, the system has locked the whole table. Other transactions can
no longer access any of the records in the table to make changes.

System Response

The table-wide lock obstructs other running transactions and should
generally be avoided.

How to fix this error?

Increase the size of the memory area available to applications to store
locks using the database parameters LOCKLIST and MAXLOCK.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB6118 - Too many lock escalations occur in the system ?

  The SAP error message DB6118, which indicates "Too many lock escalations occur in the system," typically arises when the database system is experiencing a high number of lock escalations. Lock escalation occurs when a database system converts many row-level locks into a table-level lock to reduce the overhead of managing numerous locks. This can lead to performance issues and contention for resources.
  Causes:
  
  High Concurrency: A large number of transactions trying to access the same data simultaneously can lead to many row-level locks, prompting the database to escalate to table-level locks.
  Long-Running Transactions: Transactions that hold locks for an extended period can increase the likelihood of lock escalations.
  Insufficient Lock Management: The database configuration may not be optimized for the workload, leading to excessive lock escalations.
  Inefficient Queries: Poorly designed queries that access a large number of rows can contribute to lock contention.
  Database Configuration: The database parameters related to locking and memory management may not