IBM Support

PI47212: END UNDO/REDO/TODO RECORDS ARE NOT RECOGNIZED AFTER A DB2 OUTAGE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 V11 changed the offset and length of URIDs stored in END
    UNDO/REDO/TODO records.  IIDR CDC for z/OS does not account for
    this, and so is unable to recognize any of these records when
    they are written after a DB2 RESTART.  This can leave a UR
    hanging in the Staging Space.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IIDR CDC for z/OS who experience a  *
    *                 DB2 outage.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: After a DB2 outage, incomplete Units of *
    *                      Recovery (URs) will be disposed of by   *
    *                      DB2 when DB2 is restarted by writing    *
    *                      END UNDO/TODO/REDO records to the log.  *
    *                      With DB2 V11, the location within these *
    *                      records of the URID for the UR being    *
    *                      disposed of has changed.  IIDR CDC for  *
    *                      z/OS is not accessing the URID in its   *
    *                      new position, so it never finds that    *
    *                      the UR has been completed.  Such URs    *
    *                      will remain in the Staging Space        *
    *                      indefinitely, until some action is      *
    *                      taken to remove them.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    
    URs terminated by DB2 after an outage may remain in the Staging
    Space indefinitely.
    

Problem conclusion

  • Logic has been adjusted to access the URID in the proper
    location of DB2 V11 END UNDO/TODO/REDO log records.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI47212

  • Reported component name

    INFO SRVR CDC Z

  • Reported component ID

    5655U7600

  • Reported release

    A21

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-19

  • Closed date

    2015-09-28

  • Last modified date

    2016-04-27

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

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

    UI31571

Modules/Macros

  •    CHCDXLDL
    

Fix information

  • Fixed component name

    INFO SRVR CDC Z

  • Fixed component ID

    5655U7600

Applicable component levels

  • RA21 PSY UI31571

       UP15/10/06 P F510

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTVMA","label":"InfoSphere Data Replication for DB2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2016