PI97455: REPLICATION OF SUBS BY PARTITIONS MAY NOT DETECT/HANDLE TARGET CONFLICTS IF ROWS ARE MISSING ON TARGET CAUSING SILENT DATA LOSS

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Q Apply using  subscription by partitions may not detect or
  report target conflicts when rows are missing from target and
  an update on source causes that row to move across partitions.
  This may result in target data divergence without any
  EXCEPTIONS reported or rows staged in DELAYIN table.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- Q Apply using Subscriptions by            *
  *                 Partitions                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- Q Apply using subscription by        *
  *                      partitions may not detect or report     *
  *                      target conflicts when rows are missing  *
  *                      from target and an update on source     *
  *                      causes that row to move across          *
  *                      partitions.  This may result in target  *
  *                      data divergence without any EXCEPTIONS  *
  *                      reported or rows staged in DELAYIN      *
  *                      table.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- Replication of subscriptions by partitions should always use
  partition limit key range predicate in the WHERE clause used
  for applying DELETE or UPDATE statements.  Otherwise, Q Apply
  may not detect true conflicts on target and end up applying
  DELETE or UPDATE operations out of order with other row
  operations on same replication key but belonging to a different
  partition subscription. Consequently it may result in data
  divergence or data loss without any EXCEPTIONS reported, or
  rows in DELAYIN table.
  

Problem conclusion

Temporary fix

Comments

• 1- Q Apply is fixed to always use partition limit key range
  predicate in the WHERE clause used for applying DELETE or
  UPDATE statements, so that it can detect target missing row
  conflicts.
  ASNCLP was not updated.
  

APAR Information

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

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

  UI56572 UI56573 UI56574 UI56575

Modules/Macros

•    ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCCMD
  ASNMCMD  ASNMON   ASNQACMD ASNQAPP  ASNQAROW ASNQCAP  ASNQCCMD
  ASNQDEP  ASNQEXRP ASNQMFMT ASNQXFMT ASNRBASE ASNTDIFF ASNTDSP
  ASNTRC   ASN2BASE
  

Fix information

• Fixed component name

  WS REPLICATION

• Fixed component ID

  5655L8800

Applicable component levels

• RB33 PSY UI56572

     UP18/06/23 P F806

• RB34 PSY UI56573

     UP18/06/26 P F806

• RB35 PSY UI56574

     UP18/06/23 P F806

• RB36 PSY UI56575

     UP18/06/23 P F806

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.