JR37484: REPLICATION ENGINE FIXES FOR DB2 LUW V9.1 FP10

DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as new function.

Error description

Local fix

Problem summary

• .
  The following Replication Server engine defects have been
  fixed in DB2 LUW V9.1 FP10:
  .
  .
  787719:QCAPTURE:Possible SIGILL during log reading when
  connected to a DPF system.
  .
  User Affected: Q/SQL CAPTURE for LUW
  .
  Problem Description: A timing issue (race condition)
  between two components of Capture during transaction
  processing (process log records) and transaction
  publishing may cause a SIGILL.
  .
  Problem Summary: SIGILL may be encountered in the log
  reader thread when processing transactions in a DPF
  environment. Capture stops.
  .
  Problem Conclusion: The problem has been fixed.
  .
  .
  Defect 793037: asnmon capture latency error when capture
  server in COMMA SEPARATED DECIMAL env
  .
  User Affected: ASNMON
  .
  Problem Description: The computed capture latency is
  error.  The monitor program only deals with time
  difference in the format of '00000000000014.811353'.
  However, in the customer's enviroment, the output of time
  difference is '00000000000014,811353', where the separator
  between seconds and microseconds is a comma.  This is
  because the customer runs with COMMA as the delimiter of
  DECIMAL.  ASNMON has been fixed to deal with the COMMA.
  .
  .
  Defect 796894: asnqcap takes snapshot every 2 seconds,
  which cause dblatch issues on database.
  .
  User Affected: QCAPTURE
  .
  Problem Description: Removing a call to a DB2 function
  that is frequently issued by QCAPTURE as it causes latch
  contention and slowdown in DB2.
  .
  .
  Defect 789013: missing row when commit_count>0, RI
  violation is encountered during the cycle
  .
  User Affected: SQLAPPLY
  .
  Problem Description: Apply advances set synchpoint
  incorrectly after RI violation was detected and retried,
  which results in missing data in target table.  This
  problem can occur to subscriptions of read only target
  type with COMMIT_COUNT>0, or update anywhere type
  subscriptions.
  .
  .
  Defect 782980: Restart in partitioned environments could
  result in loss of partial transaction
  .
  User Affected: LUW QCAPTURE and SQLCAPTURE in DB2 DPF
  environments
  .
  Problem Description: Part of a global transaction could be
  skipped (not published) during the restart or reinit of a
  QCAPTURE or SQLCAPTURE program.
  .
  Problem Summary: A timing condition exists which could
  result in part of a global transaction being skipped
  after evaluating a global prepare log record timestamp.
  .
  Problem Conclusion: The problem has been fixed.
  .
  

Problem conclusion

• refer to the previous section
  

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:

  JR37852 IC71499 IC71500

Fix information

• Fixed component name

  REPLICATION SER

• Fixed component ID

  5724N9800

Applicable component levels

• R910 PSY

     UP