JR64176: USER-SET JOURNAL CONTROL FIELDS IN AUDIT KCOPS COME OUT NON-NULLABLE, BUT SHOULD BE NULLABLE

APAR status

• Closed as program error.

Error description

• User-set audit JCFs are non-nullable, but should be nullable in
  KcopSingleRowAvroAuditIntegrated and
  KcopJsonSingleRowAuditFormatIntegrated when set using the
  configuration audit.jcfs. For instance, in response to an insert
  event on the source, the journal control field ENTTYP when
  nullable appears as "A_ENTTYP":{"string":"PT"}. However, when it
  is non-nullable, it appears as "A_ENTTYP":"PT". Potentially, if
  the source sends a NULL for a user-set audit journal control
  field, a serialization exception occurs and the subscription
  fails.
  

Local fix

• This defect occurs in build 5603. A temporary workaround is to
  modify the source code of the affected KCOPs shipped in the
  samples.jar. Specifically, for
  KcopJsonSingleRowAuditFormatIntegrated.java, line 195 should be
  changed from:
  
  avroJournalControlFields =
  jCFBuilder.buildListOfJournalControlFields(auditJCFs, false);
  
  to:
  
  avroJournalControlFields =
  jCFBuilder.buildListOfJournalControlFields(auditJCFs, true);
  
  
  And identically for KcopSingleRowAvroAuditHeadersIntegrated.java
  line 568.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue might affect you if you use audit KCOPs           *
  * KcopSingleRowAvroAuditIntegrated and                         *
  * KcopJsonSingleRowAuditFormatIntegrated with CDC for Kafka    *
  * 11.4.0.4-5603 or earlier.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CDC tries to write "null" values to audit fields in Kafka    *
  * topics where the fields were configured as not nullable.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.4-5607 or newer for Kafka.             *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.4-5607 or newer for Kafka resolves 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

  IDR KAFKA

• Fixed component ID

  5725E30KA

Applicable component levels