GG04788: REPLICATION ENGINE FIXES FOR DB2 LUW V8.2 FP18

APAR status

• Closed as program error.

Error description

Local fix

Problem summary

• The following Replication Server defects have been fixed
  in DB2 LUW V8FP18:
  .
  Defect 379746: SQL Analyzer is not detecting the IS_KEY
    information correctly
  User Affected: asnanalyze
  Problem Description: asnanalyze is not dealing properly
    long index names.  Customers using asnanalyze having
    multiple indexes with long lengths will get wrong
    results.
  Problem Conclusion: Increase the allocated size for
    holding index names.
  .
  Defect 380789: ABENDS: Browser terminates too early
    before Agents exit.
  User Affected: QAPPLY on Sun64
  Problem Description: In case of an ungraceful agent
    thread termination, browser may terminate too early
    without waiting long enough for all its agents to stop.
    This could lead to agents referencing browsers deleted
    objects and ABENDS.
  Problem Summary: Browser termination and cleanup needs to
    wait long enough for all its agents to terminate before
    it for all scenarios.
  Problem Conclusion: Added browser patience to wait for all
    agents to terminate before clean up and stopping.
  .
  Defect 381672: The LONG VARCHAR type from the source table
    can't be mapped to the VARCHAR type of the target table
  Problem Description: The root cause of the problem was in
    QAPPLY's retry logic to handle the deadlock/timeout.
    When deadlock is encountered, QAPPLY retries the steps
    for validating and activating the sub.  However it did
    not reset in-memory state of the SchemaMsg column info
    leading to incorrect identify of the column type during
    the subsequent attempt (retry).  Fix is to maintain a
    local copy of column info in a re-entrant safe manner.
  .
  Defect 380877: Before values for LOB/XML should not be
    counted in max message size estimate
  User Affected: QCAPTURE
  Problem Description: QCAPTURE was counting the LOB and XML
    columns for before values in max message size estimation
  Problem Summary: QCAPTURE should set not count those
    columns because they are never sent
  Problem Conclusion: QCAPTURE is now excluding those
    columns in max message size estimate
  .
  Defect 380912: stmt owner should be invalidated in
    getPreparedStmt() if handle is stolen, QCAPTURE should
    stop and not deactivate active subs in case of errors
    other than a permanent compression dictionary error
  User Affected: QCAPTURE
  Problem Description: stmt owner was not invalidated in
    getPreparedStmt() and QCAPTURE was invalidating
    subscriptions when error
  Problem Summary: stmt owner should be invalidated when
    the handle is stolen, and QCAPTURE should come down for
    subscription errors
  Problem Conclusion: stmt owner is now invalidated when the
    handle is stolen, and QCAPTURE comes down for
    subscription errors
  .
  Defect 381674: SQL519 error after reinitialized QCAPTURE
    and insert 'CAPSTART'
  User Affected: QCAPTURE
  Problem Description: QCAPTURE should did not close the
    cursor when there's a non-zero SQLCODE while loading
    subscriptions
  Problem Summary: QCAPTURE should close cursor and commit
    DB2 upon SQL errors while loading subscriptions
  Problem Conclusion: QCAPTURE is now closing cursor and
    committing DB2 upon SQL errors while loading
    subscriptions
  .
  Defect 380693: update anywhere with conflict_level=2, -107
    when before image > 18 bytes for compensation
  User Affected: SQLAPPLY
  Problem Description: SQLAPPLY constructed before image
    name longer than 18 bytes when source has 18-byte limit
  Problem Summary: SQLAPPLY should truncate before image
    name to 18 bytes when source has 18-byte limit
  Problem Conclusion: SQLAPPLY is changed to truncate
    before image name to 18 bytes if source supports
    18-byte limit
  .
  Defect 380755: SQLAPPLY fails with ASN1016 for
    disable_refresh=1, when the member has loadx_type=6 or
    MEMBER_STATE='D'
  User Affected: SQLAPPLY
  Problem Description: SQLAPPLY fails with ASN1016 for
    disable_refresh=1, when the member has loadx_type=6 or
    MEMBER_STATE='D'
  Problem Summary: SQLAPPLY should not issue error message
    ASN1016 for members with loadx_type=6 or
    MEMBER_STATE='D'
  Problem Conclusion: SQLAPPLY will not detect setting of
    disable_refresh for members with loadx_type=6 or
    MEMBER_STATE='D'
  .
  Defect 380822: Linux 64 bit - corrupted char data from
    ZOS to Linux 64 bit target
  User Affected: SQLAPPLY
  Problem Description: SQLAPPLY on Linux 64 bit inserts
    corrupted data to target table
  Problem Summary: Linux SQLAPPLY tags CHAR field with
    incorrect CCSID
  Problem Conclusion: retrieve and tag CHAR fields with
    correct CCSID
  .
  Defect 381276: LOB data is not replicated when key columns
    are defined as not null
  User Affected: SQLAPPLY
  Problem Description: SQLAPPLY does not replicate correct
    LOB value when key column is defined as not null
  Problem Summary: SQLAPPLY incorrectly check the null
    indicator when the key column is defined as not null and
    retrieved wrong LOB value from source table
  Problem Conclusion: do not check null indicator if key
    column is defined as not null so that LOB value can be
    retrieved correctly from source table
  .
  Defect 381310: rows are missing when RI violation is
    encountered during transactional processing
  User Affected: SQLAPPLY
  Problem Description: rows are missing when RI violation is
    encountered during transactional processing
  Problem Summary: SQLAPPLY incorrectly advanced set
    synchpoint when RI violation errors occurred during the
    cycle
  Problem Conclusion: with this fix, SQLAPPLY will not
    advance set synchpoint when RI violation errors occurs
  .
  Defect 381311: SQLAPPLY generates RI violation information
    without restarting Apply
  User Affected: SQLAPPLY
  Problem Description: Currently users need to stop and
    restart SQLAPPLY with trace options to collect RI error
    information
  Problem Summary: users should be able to collect RI
    violation information without restarting Apply
  Problem Conclusion: with this fix, user can find RI
    violation information in file apply_qual.RI in Apply
    path
  .
  

Problem conclusion

• The defects listed in this APAR have been
  fixed, and are available in DB2 LUW V8.2 FP18
  

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:

Modules/Macros

• NOE
  

Fix information

• Fixed component name

  DATAPROPAGATOR

• Fixed component ID

  5765DP800

Applicable component levels

• R820 PSY

     UP