IBM Support

PI63384: IF DB2 V11 IS RUNNING IN EITHER CM OR NFM, A DB2 OUTAGE WILL CAUSE URS TO REMAIN UNCOMPLETED IN THE STAGING SPACE.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2 V11 running in either CM or NFM Mode writes END-xxDO log
    records that don't always contain the URID value in the LRH
    header area.  Thus there are three places from which the URID
    can be found, in the LRH and two fields in the UR Control Record
    main part.  Logic must be robust enough to obtain the URID no
    matter which field in which it is presented.
    

Local fix

  • No local fix is available.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 V11.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When DB2 V11 is being used, depending   *
    *                      on the execution mode (CM vs. NFM), it  *
    *                      produces log records in the same format *
    *                      as DB2 V10 or in the new format for DB2 *
    *                      v11, but it up-converts the DB2 V10     *
    *                      headers to DB2 V11 format when an       *
    *                      application using IFCID 306 requests    *
    *                      log data.  It does not up-convert the   *
    *                      data payload of log records.  For END-  *
    *                      xxDO records, this produces records     *
    *                      that appear to be DB2 V11, but contain  *
    *                      their data content in DB2 V10 format.   *
    *                      This content includes the URID of the   *
    *                      UR for which the END-xxDO record was    *
    *                      written.  Addtionally, DB2 V11 NFM does *
    *                      not always fill in the URID in the LRH  *
    *                      for all types of END-xxDO records.  For *
    *                      these different combinations, if the    *
    *                      URID is not obtained properly from the  *
    *                      END-xxDO log records, the URs that were *
    *                      open at the time of a DB2 failure will  *
    *                      be open indefinitely in the Staging     *
    *                      Space after DB2 restarts.               *
    ****************************************************************
    * RECOMMENDATION: APPLY CORRECTIVE SERVICE                     *
    ****************************************************************
    URs that are recovered after DB2 restarts after a failure will
    not close in the Staging Space.
    

Problem conclusion

  • For DB2 V11, the URID will be accessed from the LRH and from
    the log record data for END-xxDO records, wherever it is found
    to be non-zero.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI63384

  • 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

    2016-05-31

  • Closed date

    2016-06-15

  • Last modified date

    2016-07-04

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

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

    UI38702

Modules/Macros

  •    CHCDXLDL
    

Fix information

  • Fixed component name

    INFO SRVR CDC Z

  • Fixed component ID

    5655U7600

Applicable component levels

  • RA21 PSY UI38702

       UP16/06/30 P F606 Ž

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.



Document information

More support for: InfoSphere Data Replication for DB2 for z/OS

Software version: 10.2.1

Reference #: PI63384

Modified date: 04 July 2016


Translate this page: