JR64910: EXTENDED ROW VARBINARY DATA CAUSES PARSER ERROR

APAR status

• Closed as program error.

Error description

• The following error occurs:
  IBM InfoSphere Data Replication will be shutdown due to an error
  while parsing logs for table BCIS.TRAVEL_DOCUMENT_CERTIFICATE at
  position 0000000000000040ebd60000000003957b03. The table
  definition may have changed. Please re-add the table definition
  and refresh this table. The issue can also be resolved by
  parking the table.
  Error: newPosition > limit: (32891 > 404)
  
  Db2 LUW sets the sign bit in the 2-byte short offset of a column
  to indicate it is stored in extended storage. But, CDC will only
  treat this as an extended row if it is an "extended row
  datatype". Currently CDC only considers the datatypes VARCHAR
  and VARGRAPHIC to be extended row datatypes. Thus, it does
  handle the VARCHAR FOR BIT DATA extended row data as extended
  row data and the parser error occurs.
  

Local fix

• Increase the pagesize of the table so the pagesize exceeds the
  maximum size for any VARCHAR FOR BIT DATA or VARBINARY column.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue might affect you if you are replicating from Db2  *
  * tables with VARCHAR FOR BIT DATA/VARBINARY column that do    *
  * fit in the page.                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Replication was stopping with a parser error when CDC        *
  * encountered data from a VARCHAR FOR BIT DATA/VARBINARY       *
  * column that did not fit in the page, i.e. "extended row      *
  * data".                                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.4-5640 or newer for Db2 LUW.           *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.4-5640 or newer for Db2 LUW 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

  IS DATA REPLICA

• Fixed component ID

  5725E3000

Applicable component levels