JR62454: IDR OPERATIONS ARE NO LONGER LOST ON A TABLE PARTITIONED ON MORE THAN ONE DPF NODE

APAR status

• Closed as program error.

Error description

• Data loss if DDL performed on a table partitioned on more than
  one node. When the problem occurs, only operations from
  partitions with the lowest DPF node number are replicated.
  Operations from higher node numbers are lost. This occurs
  because the log parser was creating a table definition and
  committing it to the history when it saw the "DM" log record
  for the table from the node with the lowest node number that
  the table is partitioned on. This commit only contains an
  "interval" for this lowest-numbered partition. When the log
  parser see the DM records for the subsequent partitions, it was
  adding an interval for them but in a separate transaction. If
  the log parser was interrupted before it could commit these
  additional intervals, the table definition was left with an
  interval for only the lowest-numbered partition(s). If this
  table definition is then subsequently used any operations on
  the partitions without an interval will not be replicated. The
  fix is to commit the table definition and all of its intervals
  in one transaction.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue may affect you if you are using CDC for LUW       *
  * version older than 11.4.0.2-5563.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Data loss if DDL performed on a table partitioned on more    *
  * than one node.                                               *
  * When the problem occurs, only operations from partitions     *
  * with the lowest DPF node number are replicated.              *
  * Operations from higher node numbers are lost.                *
  * This occurs because the log parser was creating a table      *
  * definition and committing it to the history when it saw the  *
  * "DM" log record for the table from the node with the lowest  *
  * node number that the table is artitioned on. This commit     *
  * only contains an "interval" for this lowest-numbered         *
  * partition.                                                   *
  * When the log parser see the DM records for the subsequent    *
  * partitions, it was adding an interval for them but in a      *
  * separate transaction.                                        *
  * If the log parser was interrupted before it could commit     *
  * these additional intervals, the table definition was left    *
  * with an interval for only the lowest-numbered partition(s).  *
  * If this table definition is then subsequently used any       *
  * operations on the partitions without an interval will not be *
  * replicated.                                                  *
  * The fix is to commit the table definition and all of its     *
  * intervals in one transaction.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.2-5563 or newer for 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 CDC DB2 LUW

• Fixed component ID

  5725E30DL

Applicable component levels