IBM Support

PK01336: RC00E20003 STORAGE SHORTAGE IN THE DIST ASID

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DDFL09 DB2DRDA DB2INACTIVE defect pk01336 dpk01336
    ABEND04E RC00E20003 DSNSVBK for a storage shortage in the DDF
    DIST asid (xxxDIST). The DIST asid may have a large accumulation
    of storage for DDXB Storage Pool and for DDGB/DDAN Storage Pool
    .
    ***********************************
    Additional symptoms and keywords:
      ABEND04E AB04E S004E 04E 04E-00E20003 00E20003 RC00E20003
        DSNSVBK DSNSVBK+0604 0604
    
      LCOMDDS1 "DDGB/DDAN Storage Pool"
      LCOMDDS3 "DDXB Storage Pool"
      DDGBVSTG "DDIS Agent Storage Pool"
      DDGBGSTG "DDIS GLOBAL STORAGE POOL"
      DDGBLSTG "DDIS LARGE VAR STG POOL"
      SOS SHORT ON STORAGE ABEND878 AB878 S0878
      Subpool sub pool 231 subpool231 sp231 key 7 key7
      The lost DDGB and DDXB storage will not be released until
      the entire DB2 subsystem is stopped.
    
      DDF Inactive Thread support
      DSNTIPR DDF THREADS INACTIVE
      DSN6FAC CMTSTAT INACTIVE
    
      Hop Hopping
    
      The excessive storage utilization may also lead to performance
      degradation, in some cases, severe.  Situations may be
      encountered where remote client applications would either
      timeout (522 ABEND522 S522 AB522 if DB2 z/OS was the client
      system) or suffer sever performance degradation due to lack
      of through-put of a DB2 z/OS subsystem (accessed as a server).
      Many server threads may be found to be suspended waiting for
      latches or are just not being dispatched by the operating
      system because available CPUs resources were constrained due
      to dealing with unusually long storage pool chains.  That is,
      excessive CPU usage may be caused by a lot of VSM activity due
      to DB2 z/OS attempting to compact storage pools. The excessive
      storage pool utilization leads to longer latch hold times
      which further contributes to the lack of server thread
      through-put.
    DB2STGLK/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    *                 Specifically, where DB2 is configured with   *
    *                 DDF THREADS = INACTIVE specified             *
    *                 (DSN6FAC CMTSTAT INACTIVE).                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Excessive utilization of DDIS DDGB      *
    *                      ("DDGB/DDAN Storage Pool") and DDXB     *
    *                      ("DDXB Storage Pool") storage may,      *
    *                      over time, lead to a short on           *
    *                      storage condition in the xxxxDIST       *
    *                      address space ECSA storage,             *
    *                      subpool 231 Key 7.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Excessive utilization of DDIS DDGB ("DDGB/DDAN Storage Pool")
    and DDXB ("DDXB Storage Pool") Subpool 231 Key 7 storage.
    DDGB storage (and its associated DDXB storage) may be
    lost.  This problem will only occur if DB2 is configured with
    DDF Inactive Thread support and remote client application
    SQL causes DB2 server threads to "hop" to secondary remote
    servers via DRDA protocols.  Even then, the lost of storage
    MAY only occur if the hop connection is somehow terminated.
    

Problem conclusion

  • DB2 has been changed to properly manage the use of DDIS DDGB
    storage.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PK01336

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-02-17

  • Closed date

    2005-03-01

  • Last modified date

    2011-02-26

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

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

    UK01033 UK01034

Modules/Macros

  •    DSNDDPSB DSNLAGNX DSNLQACT DSNLQDIS
    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R710 PSY UK01033

       UP05/03/17 P F503 Ž

  • R810 PSY UK01034

       UP05/03/17 P F503 Ž

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":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 May 2020