PM64226: GROWTH OBSERVED FOR DSNDB01.SYSDBDXA WHEN A LONG READ CLAIM IS HELD ON THE OBJECT.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Growth observed for DSNDB01.SYSDBDXA when a long READ CLAIM is
    held on the object.
    This may happen not only for SYSDBDXA but also for other DB2
    CATALOG and DIRECTORY LOBs. The problem happens when an old
    READLRSN exists on the object. The problem can be observed in
    both DATASHARING and NON-DATASHARING systems.
    Additional symptoms: ABEND 04E 00D79999 DSNPXTN1
                         00C90101 DSNOALLO ERQUAL 5002
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 V10 for z/os datasharing users       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The LOB table spaces associated with    *
    *                      the DB2 directory data base (DSNDB01)   *
    *                      could experience significant space      *
    *                      growth resulting from BIND/REBIND       *
    *                      operations, DDL, utility activity       *
    *                      such as REORG or other symptoms such    *
    *                      as :                                    *
    *                      1. ABEND04E RC00D79999 of DSNPXTN1      *
    *                      2. zero pages                           *
    *                      3. RC00C90101 DSNOALLO ERQUAL5002       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The lowest read claim LRSN value from all data sharing members
    is used to determine whether deleted LOB space can be reused.
    When the read claim value is being updated frequently during
    the BIND/REBIND processing, or as a result of DDL or REORG
    activity, delays may occur in broadcasting this value to
    other data sharing members. Therefore, the deleted space within
    directory LOB pagesets may not be reused soon enough, causing
    space growth.
    

Problem conclusion

  • DB2 code is changed to allow the deleted LOB space to more
    quickly be reused by an inserter that is running in the same
    data sharing member without dependence upon the global read
    read claim LRSN. This change is limited to LOB table spaces
    residing within the DB2 directory data base (DSNDB01), i.e.
    DSNDB01.SYSDBDXA, DSNDB01.SYSSPUXA, DSNDB01.SYSSPUXB.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM64226

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-09

  • Closed date

    2012-11-01

  • Last modified date

    2012-12-04

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

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

    UK83215

Modules/Macros

  •    DSNOALLO DSNODALN DSNODEAL
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK83215

       UP12/11/20 P F211

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM64226

Modified date:

2012-12-04

Translate my page

Machine Translation

Content navigation