PI88530: CAPTURE IGNORES ALTER ADD COLUMN DDL IF THERE ARE MORE THAN 20 ADDCOLS FOR A SUB.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• When you do more than 20 alter add column for a sub and commit
  after 20 alter add, Capture only processes 20 alter add columns
  and ignores the rest.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- SQL Apply users                           *
  *                 2- Q Capture users                           *
  *                 3- QApply users                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- Data loss in SQL Apply after adding  *
  *                      new members to existing subscription    *
  *                      set                                     *
  *                      2- When you do more than 20 alter add   *
  *                      column for a sub and commit after 20    *
  *                      alter add, Capture only processes 20    *
  *                      alter add columns and ignores the       *
  *                      rest.                                   *
  *                      3- When an apply agent receives a       *
  *                      normal signal: SIGTERM, SIGINT,         *
  *                      SIGUSR1, or SIGUSR2, then ASN0569E      *
  *                      message is sent to the Apply log.       *
  *                      Message is only needed for more         *
  *                      serious abends.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- SQL Apply incorrectly updated the synchpoint value in the
  ibmsnap_prune_set after adding a new member to an existing
  subscription set as non condensed non complete CCD target. As a
  result, the Capture program pruned the rows in the CD table
  that have been not processed and the changed data is lost for
  ever.
  2- Both ADDCOL DDL and ADDCOL signal should follow the existing
  limitation that the max ADDCOL DDL/signal of each transaction
  is 20.
  3- When an apply agent receives a normal signal: SIGTERM,
  SIGINT, SIGUSR1, or SIGUSR2, then ASN0569E message is sent to
  the Apply log. Message is only needed for more serious abends..
  

Problem conclusion

Temporary fix

Comments

• 1- SQL Apply is changed not to update the ibmsnap_prune_set
  synchpoint when adding a new member to an existing subscription
  set.
  2- With this fix, Capture will process all alter add columns
  and ADDCOL signal for a sub as long as the user does a DB2
  commit after 20 Alter ADD columns or ADDCOL signals.
  3- Check signal type and if it is SIGINT, SIGTERM, SIGUSR1, or
  SIGUSR2, then output alternate debug message instead.
  Note: ASNCLP has been updated from db2_v105fp10 s171203.
  

APAR Information

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

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

  010PC2Ÿ UI52680 UI52681 UI52682 UI52683

Modules/Macros

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

     UP17/12/22 P F712

• RA24 PSY UI52681

     UP17/12/22 P F712

• RA25 PSY UI52682

     UP17/12/22 P F712

• RA26 PSY UI52683

     UP17/12/22 P F712

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.