SAP Knowledge Base Article - Preview

3027718 - Parallel DSI cause deadlocks - SRS

Symptom

  • In rare circumstance, parallel DSI might get the following deadlock situation:
    • This thread exceeded the configured dsi_commit_check_locks_log executions of deadlock detection while waiting to commit. 
    • 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 = <RDS>.<RDB>, qid=0003000d1f55f64b003f74df0014003f74c800030000acd800c424610000000000000003. 

  • Here are related parallel DSI parameters:
    • dsi_num_threads 2
    • dsi_commit_check_locks_intrvl 1000 
    • dsi_commit_check_locks_log 200
    • dsi_commit_check_locks_max 400
    • dsi_serialization_method wait_for_commit


Read more...

Environment

  • SAP Replication Server (SRS) 15.7.1
  • SAP Replication Server (SRS) 16.0

Product

SAP Replication Server 15.7 ; SAP Replication Server 16.0 ; SAP Replication Server 16.1 ; SAP Replication Server all versions

Keywords

parallel dsi; dsi_num_threads;dsi_commit_check_locks_log; dsi_commit_check_locks_max; dsi_commit_check_locks_intrvl , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , How To

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.