SAP Knowledge Base Article - Preview

2801588 - High volume of duplicate key errors brings DSI down. Outbound queue is building up.- SRS


  • The DSI thread is Down due to the Error 2601:  

ERROR #1028 DSI EXEC(146(1) MYDS.MYDB) - neric/dsi/dsiqmint.c(5172)
Message from server: Message: 2601, State 1, Severity 16 -- 'Attempt to insert duplicate key row in object 'MYTABLE' with unique index 'PK_MY_COLUMN''.
Message from server: Message: 3621, State 0, Severity 10 -- 'Command has been aborted.'.
THREAD FATAL ERROR #5049 DSI EXEC(146(1) MYDS.MYDB) - neric/dsi/dsiqmint.c(5185)
The DSI thread for database 'MYDS.MYDB' is being shutdown. DSI received data server error #2601 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #1 mapped from input command #3 of the failed transaction. 

  • Skipping the first transaction in the outbound queue helps to bring the DSI thread up, but it then fails again due to Error 2601. It looks like there are too many transactions hitting duplicate key errors in this replicate table. 
  • After a few skipped transactions, the DSI thread seems like hanging. Rebooting SRS helps to revive this connection, but then after a few skips the DSI thread gets hung again.
  • The outbound queue has built up to 2.2 GB.



SAP Replication Server (SRS) 16.0


SAP Replication Server 16.0


autocorrection, dsi_command_convert, i2di ,u2none, dsi_row_count_validation, sts_cachesize, sts_full_cache, unresponsive, hung, configure , 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.