SAP Knowledge Base Article - Preview

3578199 - DSI Hang with message: This thread exceeded the maximum configured dsi_commit_check_locks_max executions of deadlock detection while waiting to commit

Symptom

  • DSI is stuck when there is large transaction rollback with the following messages  reported in RepServer logs. 

DSI: This thread exceeded the configured dsi_commit_check_locks_log executions of deadlock detection while waiting to commit. Connection = xxx.xxx, qid=003e0403d53faf2d65f04764003265e45d7500420000b287012b4ae40000000000000001.
DSI: This thread exceeded the configured dsi_commit_check_locks_log executions of deadlock detection while waiting to commit. Connection = xxx.xxx, qid=003e0403d577800d65f12ef7001165e45d7500420000b287012b4ae40000000000000001.
DSI: This thread exceeded the maximum configured dsi_commit_check_locks_max executions of deadlock detection while waiting to commit. It will be rolled back and resubmitted. Connection = xxx.xxx, qid=003e0403d53faf2d65f04764003265e45d7500420000b287012b4ae40000000000000001.
DSI: This thread exceeded the maximum configured dsi_commit_check_locks_max executions of deadlock detection while waiting to commit. It will be rolled back and resubmitted. Connection = xxx.xxx, qid=003e0403d577800d65f12ef7001165e45d7500420000b287012b4ae40000000000000001.

  •  DSI resumes automatically after the rollback completes.(It may take some time and might cause OBQ increasing)


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 with High Availability Disaster Recovery (HADR) for Business Suite

Product

SAP NetWeaver Application Server for ABAP innovation package all versions ; SAP Replication Server 16.0

Keywords

KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.