How To Fix DB6115 - Number of deadlocks per day

DB6115 - Overview

• Message type: E = Error

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

• Message number: 115

• Message text: Number of deadlocks per day

What causes this issue?

A Deadlock is a mutual lock of two or more running transactions. It
means that they are both in a wait state and each is waiting for the
other.
Example:
T1 holds lock A and requires lock B.
T2 holds lock B and requires lock A.
The system resolves this wait situation by resetting one of the
transactions after a certain wait time has expired.

System Response

The waiting processes are blocked during the wait state.

How to fix this error?

Confirm which applications are caught in the deadlock situation and, if
necessary, modify these applications. You should also observe the lock
escalations, as these can also lead to deadlocks.
You can shorten the times for which the processes involved are blocked
using the database configuration parameters LOCKTIMEOUT and DLCHKTIME.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB6115 - Number of deadlocks per day ?

  The SAP error message DB6115 indicates that the number of deadlocks occurring in the database has exceeded a predefined threshold within a day. Deadlocks happen when two or more transactions are waiting for each other to release locks, causing a standstill. This can lead to performance issues and may affect the overall stability of the SAP system.
  Causes of DB6115
  
  High Concurrency: Multiple transactions trying to access the same resources simultaneously can lead to deadlocks.
  Locking Strategy: Inefficient locking strategies or inappropriate isolation levels can increase the likelihood of deadlocks.
  Long-Running Transactions: Transactions that take a long time to complete can hold locks for extended periods, increasing the chance of deadlocks.
  Database Design: Poorly designed database schemas or indexes can lead to inefficient access patterns, contributing to deadlocks.
  Application Logic: Inefficient application logic that leads to multiple transactions trying to access the same resources in different orders.
  
  Solutions to DB6115
  
  Analyze Deadlock Logs: Use database tools to analyze