Message type: E = Error
Message class: DB6 - DB6: Alert Monitoring and Alert Configuration
Message number: 120
Message text: Too many exclusive lock escalations occur in the system
As a transaction is exclusively accessing too many records in a table,
the system has locked the entire table. Other transactions can no
longer access any records in the table, even to read them.
The table-wide exclusive lock is significantly obstructing other
running transactions and should generally be avoided.
Increase the amount of memory available to an application to store
locks using the database parameters LOCKLIST and MAXLOCK.
Error message extract from SAP system. Copyright SAP SE.
DB6120
- Too many exclusive lock escalations occur in the system ?The SAP error message DB6120 indicates that there are too many exclusive lock escalations occurring in the system. This typically happens when the database is trying to manage locks for transactions, and it is unable to do so efficiently, leading to performance issues and potential deadlocks.
Cause: High Lock Contention: This can occur when multiple transactions are trying to access the same data simultaneously, leading to a situation where the database has to escalate from row-level locks to page-level or table-level locks. Insufficient Lock Resources: If the database is configured with insufficient resources to handle the number of locks being requested, it may lead to escalations. Long-Running Transactions: Transactions that hold locks for an extended period can contribute to lock contention and escalations. Poorly Designed Applications: Applications that do not manage locks efficiently can lead to excessive lock escalations.
Solution: Analyze Lock Usage: Use transaction codes like SM12 (for lock entries) and SM21 (for system logs) to
Get instant SAP help. Sign up for our Free Essentials Plan.
DB6119
Number of exclusive lock escalations per hour
What causes this issue? If an application accesses database data to make changes, the system locks exactly those records in the table that are requir...
DB6118
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 trans...
DB6121
Number of lock timeouts per hour
What causes this issue? You can set the time that an application waits for a lock in the database configuration parameter LOCKTIMEOUT. After this wai...
DB6122
Too many lock timeouts occur in the system
(Copy of DB6 121)What causes this issue? You can set the time that an application waits for a lock in the database configuration parameter LOCKTIMEO...
Click on this link to search all SAP messages.