JR58975: SUBSCRIPTION FAILED TO START AFTER BOOKMARK IS SET WITH DMSETBOOKMARK COMMAND LINE UTILITY

APAR status

• Closed as program error.

Error description

• Subscription failed to start after bookmark is set with
  dmsetbookmark command line utility
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * NONE                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When bookmark is set with dmsetbookmark command line         *
  * subscription fails to start. The target engine fails with    *
  * unhandled exception:                                         *
  *                                                              *
  * 24076    2017-12-18 15:13:29.825    KAFKA002 Target Control  *
  * Channel{8776}    com.datamirror.ts.eventlog.EventLogger      *
  * logActualEvent()    Event logged: ID=1095 MSG=A fatal        *
  * communication error has occurred. Error:                     *
  * [null].Üjava.lang.NullPointerException |    at               *
  * java.util.Hashtable.put(Hashtable.java:505)|    at           *
  * com.datamirror.ts.util.kafka.KafkaJavaApiUtils.createKafkaTa *
  * rgetCommitStreamProducer(KafkaJavaApiUtils.java:116)|    at  *
  * com.datamirror.ts.target.publication.KafkaTargetPublisherPro *
  * xy.setBookmark(KafkaTargetPublisherProxy.java:1731)|    at   *
  * com.datamirror.ts.target.publication.SubscriptionLevelHandle *
  * r.setKafkaBookmark(SubscriptionLevelHandler.java:641)|    at *
  * com.datamirror.ts.target.publication.TargetPublisherProxy.ha *
  * ndleReportPositionMessage(TargetPublisherProxy.java:1557)|   *
  * at                                                           *
  * com.datamirror.ts.enginemsg.MessageDispatcher.dispatchSwitch *
  * (MessageDispatcher.java:451)|    at                          *
  * com.datamirror.ts.enginemsg.MessageDispatcher.dispatch(Messa *
  * geDispatcher.java:142)|    at                                *
  * com.datamirror.ts.engine.ReplicationSession.dispatchDynamicM *
  * essage(ReplicationSession.java:2818)|    at                  *
  * com.datamirror.ts.engine.ReplicationSession.dispatchControlM *
  * essage(ReplicationSession.java:2894)|    at                  *
  * com.datamirror.ts.engine.ReplicationSession$TargetControlCha *
  * nnelThread.runThread(ReplicationSession.java:1085)|    at    *
  * com.datamirror.ts.util.TsThread.run(TsThread.java:130)       *
  *                                                              *
  * Cause:                                                       *
  * At start-up time, CDC has no information on Kafka cluster    *
  * and fails to write to commit stream topic.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IIDR 11.4.0.0-5052 for all LUW engines or later   *
  ****************************************************************
  

Problem conclusion

• Upgrading to IIDR 11.4.0.0-5052 for all LUW engines or later
  will fix the issue
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IS CDC DB2 LUW

• Fixed component ID

  5725E30DL

Applicable component levels

• RB40 PSY

     UP