SAP Knowledge Base Article - Preview

3683539 - Data loss when target database is down - SRS

Symptom

Data loss when replicating from ASE to DB2 UDB via ECDA.

When problem occurred, DB2 server was not active.

Replication Server's log:

====

ERROR #1028 DSI EXEC(138(1) DCX.ddddd) - /generic/useful/cm.c(5369)
        Message from server: Message: 30291, State 0, Severity 19 -- '[[Message Iteration=1|Data Source Name=XXXXX001|SQLState=08001|Native Error=-30081|Message=[IBM][CLI Driver] SQL30081N  A communication error has been detected. Communication protocol being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location where the error was detected: "nn.nnn.nnn.nn".  Communication function detecting the error: "send".  Protocol specific error code(s): "110", "*", "*".  SQLSTATE=08001 ]

====

But DSI continued to ignore new transactions even after target DB2 was up and responsive (DSI did not receive 30291 error after DB2 is up).


Read more...

Environment

  • Replication Server 16.0 SP04 PL06
  • DirectConnect (ECDA) 15.7 SP05
  • DB2 UDB

Product

SAP Replication Server 16.0.4

Keywords

data loss, missing data, ECDA, UDB, error action, ignore error, Stop Replication, Retry and Stop, 30291, down, communication error, CR 831453, CR#831453, CR831453, 831453 , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , 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.