JR42022: IGNORE UNCHANGED LOB/XML FOR UPDATES USING EXISTING MODIFIED OFFSET IN P2P ONLY

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as new function.

Error description

• Ignore unchanged LOB/XML for UPDATEs using existing modified
  offset in P2P only.
  

Local fix

Problem summary

• Problem Description: LOB/XML columns are updated at the
  target even if they were not changed at the source in P2P
  subscriptions and Bidir/Unidir subscriptions with
  conflict_action F.
  .
  User Affected: QCAPTURE / QAPPLY
  .
  Problem Summary: LOB/XML columns are unnecessarily
  updated at the target even if the actual data was not
  updated with the same change at the source. For example,
  a non-key non-LOB/XML update at the source would result
  in an update of non-key non-LOB/XML column as well as all
  LOB/XML columns in the table. This is caused by Apply's
  inability to determine if the LOB/XML value was changed
  at the source. LOB/XML values are always sent by Capture
  to resolve possible conflicts. For non-LOB/XML columns
  Apply can determine whether or not these columns have
  been updated at the source.
  .
  Problem Conclusion: Apply is able to determine if a
  LOB/XML column was updated at the source. If it was not
  updated the LOB/XML column is not included in the update
  at the target.
  

Problem conclusion

• The problem has been fixed and will be available in
  DB2 LUW V9.5 FP9.
  

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

  WS Q-REPLIC LUW

• Fixed component ID

  5724N9801

Applicable component levels

• R950 PSY

     UP