PI94406: CAPTURE HANGS REPLICATING A LARGE TRANSACTIONAFTER A DB2 ROLLBACK IF IT HAS SPILLED THE TRANSACTION.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Capture hangs replicating a large transaction after a DB2
  ROLLBACK if it has spilled the transaction to one or more spill
  data sets.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- QApply customer                           *
  *                 2- Q Apply                                   *
  *                 3- All Capture customers                     *
  *                 4- Q Capture users using TRANS_BATCH_SZ > 1  *
  *                 5- All Capture customers.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- Q Apply may crash during STOP        *
  *                      processing if browser is stuck in       *
  *                      DONEMSG cleanup for a long time.        *
  *                      2- Q Apply should not report            *
  *                      exceptions for DUPLICATE / -803         *
  *                      sqlcode conflicts for CCD               *
  *                      subscriptions that are Condensed=Y,     *
  *                      Complete=Y . Also, DELETE conflicts     *
  *                      for row not found cannot be forced, so  *
  *                      should be reported as exceptions even   *
  *                      when REPORT_EXCEPTIONS=N.               *
  *                      3- Capture stops without displaying an  *
  *                      error message if it cannot decode a     *
  *                      SYSIBM.SYSTABLES log record.            *
  *                      4- Q Capture should support             *
  *                      TRANS_BATCH_INFO parameter setting      *
  *                      from IBMQREP_CAPPARMS table and not     *
  *                      just from command-line.                 *
  *                      5- Capture hangs replicating a large    *
  *                      transaction after a DB2 ROLLBACK if it  *
  *                      has spilled the transaction to one or   *
  *                      more spill data sets.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- Q Apply browser may get stuck a long time while cleaning
  IBMQREP_DONEMSG and corresponding applied MQ messages, during
  the program shutdown (STOP command) if there is a very high
  growth in DONEMSG entries.  Meanwhile the program Initial
  thread may call program exit which clears program memory.
  2- As per spec, Q Apply is NOT supposed to log exceptions for
  -803 (DUPLICATE) for CONDENSED CCDs. This is because -803s are
  expected to occur all the time with CONDENSED CCDs due to
  retention of DELETE rows as IBMSNAP_OPERATION='D'. Also DELETE
  conflicts for row not found cannot be forced so should always
  be reported as exceptions.
  3- Capture should display an error message before it stops it
  cannot decode a SYSIBM.SYSTABLES log record.
  4- Q Capture should allow users to set TRANS_BATCH_INFO
  parameter using IBMQREP_CAPPARMS table. For this, a new
  optional column TRANS_BATCH_INFO defined as CHAR(1) with
  default 'N' can be added to IBMQREP_CAPPARMS table.
  5- Capture hangs after calling fseeko to position to the end of
  a 1 GIG spill data set.
  

Problem conclusion

Temporary fix

Comments

• 1- Q Apply browser cleanup during program stop should time
  itself and abort if it takes too long, much before it will be
  forcefully terminated by Initial (main) thread.
  2- Q Apply is fixed to skip reporting exceptions for duplicate
  conflicts for condensed complete CCD targets and to report
  exceptions for DELETE conflicts even when REPORT_EXCEPTIONS=N.
  3- Capture will display ASN0745E before it stops if it cannot
  decode either a SYSIBM.SYSTABLES or a SYSIBM.SYSCOLUMNS log
  record.     B
  4- Q Capture is fixed to support new optional column
  TRANS_BATCH_INFO in IBMQREP_CAPPARMS table.
  5- Capture will not read transaction spill data sets if DB2
  backs out the entire transaction.
  Note: ASNCLP has been updated from db2_v105fp10 n180315.
  

APAR Information

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

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

  UI54683 UI54684 UI54685 UI54686

Modules/Macros

•    ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCCMD
  ASNCLPAP ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPMS ASNCLPQA ASNMCMD
  ASNMON   ASNQACMD ASNQAPP  ASNQAROW ASNQASUB ASNQBRWZ 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

• RA21 PSY UI54683

     UP18/04/02 P F803

• RA24 PSY UI54684

     UP18/04/02 P F803

• RA25 PSY UI54685

     UP18/04/02 P F803

• RA26 PSY UI54686

     UP18/04/02 P F803

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.