SAP Knowledge Base Article - Preview

3036910 - Replication becomes non-responsive - with no indications of issues in the logs - SRS

Symptom

  • Replication becomes non-repsonsive.  DSI is stalled.
  • There are no messages that there is an issue with the Replication Agent in the ASE primary.  The last message was a deadlock information:
    00:0073:00000:00712:20XX/02/12 02:45:15.11 server  Deadlock Id 10 detected
    Deadlock Id 10: Process (Familyid 0, Spid 712) was chosen as the victim.
    Victim process host = `user3205', user = `db_maint' program name = `RepServer' host processes = `19727'.
    End of deadlock information.
  • At the same time the RepServer received the same information:
    W. 20XX/02/12 02:45:15. WARNING #5091 DSI EXEC(143(1) myserver.mydb) - neric/dsi/dsiqmint.c(5377)
    A transaction for database 'myserver.mydb' failed. It will be retried 5 times. The data server error received (#1205) is mapped to RETRY_LOG or RETRY_STOP.

  • Deadlocks happen quite often in this environment and the above messages are normal- but in this unique case the replication stopped at precisely at 02:45.
  • Why?


Read more...

Environment

SAP Replication Server 16.0 SP03

Product

SAP Replication Server 15.7

Keywords

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 ONE Support launchpad (Login required).

Search for additional results

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