Question & Answer
Question
I got time out error. What was the cause and what should I do? CECC0325E A start replication timeout occurred. Replication will shut down for subscription XXXXXX.
Answer
The fact that when Classic CDC tried to restart replication and it timed out indicates the problem was most likely at the target. Often after these time-out's if you just try and restart again things will be fine.
Instead of recycling the server you could try restarting replication again for the subscriptions that reported the time-out. in theory enough time should have elapsed at that point for the target to allow replication to restart for the failed subscriptions. Generally these kinds of failures mean the source/target conversations are out-of-sync. The default time out value is 30 seconds.
Something else you might consider is to setup automation to periodically issue a DISPLAY,REPL,SUBSCR=*,ACTIVITY command
The output from this command will identify the last time a UOR was sent to the target. If there are committed UORs in a subscriptions capture cache and the last sent time is not changing that's an indication that the source server cannot send data to the target for that subscription.
See Example 4 in https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.3.3/com.ibm.cdcdoc.classiccdcforzos.doc/topics/iiyitoicmddisprepl.html
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22015251