Heartbeat timeout behavior of IBM Data Replication Change Data Capture

Question & Answer

Question

Event message received:

IBM Data Replication Change Data Capture heartbeat timeout has occurred. Replication will end. The timeout is currently 15 minutes. There may be a network problem or a problem on the remote system. Resolve the problem and then restart replication.

Where is this heatbeat configured ? From what server to what server ? Is it between Access Server and source instance and target instance or just between source instance and target instance? What's the frequency/interval of this heatbeat checking? Can it be changed ?

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"ARM Category":[{"code":"a8m0z000000cwbTAAQ","label":"CDC-\u003ETroubleshooting-\u003ETroubleshooting network and connectivity issues"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Version(s)","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Was this topic helpful?

Document Information

More support for:
InfoSphere Data Replication

Component:
CDC->Troubleshooting->Troubleshooting network and connectivity issues

Software version:
All Version(s)

Operating system(s):
AIX, Linux, Windows

Document number:
405521

Modified date:
16 June 2020

UID

swg21428838

IBM Support

Tips