IBM Support

PK94943: ABEND 00E20003 IN DIST WHICH IS BECAUSE DBAA SQLDA POOL IS FULL WHEN TRY TO ALLOCATE STORAGE FOR SQLDA BY 09/09/10 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DDFL09 DB2INACTIVE DB2HOP defect pk94943 dpk94943
    Get storage shortage abend 00E20003 in DIST which is because
    DBAA DDF SQLDA POO is full when try to allocate storage for
    SQLDA by DSNLXPRS +0AED UK43823. From the dump, all SQLDA are
    for same program and section. The PRC blocks which contain
    SQLDA for the same section should be getting freed during
    commit but they aren't. So many PRC block including SQLDA are
    left there.
    **************************************************************
    Additional Keywords and symptoms:
      ABEND04E AB04E S004E 04E
        04E-00E20005 00E20005 RC00E20005
          DSNLZS00.DSNSVBK+0994 DSNLZS00 DSNSVBK 0994
        04E-00E20003 00E20003 RC00E20003
          DSNLXPRS.DSNSVBK+05EA DSNLZS00 DSNSVBK 05EA
        04E-00E20004 00E20004 RC00E20004
        04E-00E2000B 00E2000B RC00E2000B
        04E-00E20015 00E20015 RC00E20015
        04E-00E20016 00E20016 RC00E20016
    DB2STGLK/K
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following abends may occur in the   *
    *                      DB2 ssnmDIST address space after        *
    *                      applying PE APAR PK68746                *
    *                      UK42748(V8)/UK42749(V9):                *
    *                      . ABEND04E-00E20003                     *
    *                          DSNLXPRS.DSNSVBK+05EA(OFFSET05EA)   *
    *                      . ABEND04E-00E20005                     *
    *                          DSNLZS00.DSNSVBK+0994(OFFSET0994)   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application using the IBM Data Server Driver for JDBC and
    SQLJ (Type 4) connects to a DB2 for z/OS server using the
    queryCloseImplicit Connection or DataSource property value of
    QUERY_CLOSE_IMPLICIT_COMMIT(3).  The application opens a query
    declared WITH HOLD and fetches all rows.  The DB2 for z/OS
    server then closes the cursor and implicitly commits.  During
    commit processing, DB2 did not clean up internal DDF control
    blocks properly.  The client repeatedly opens and fetches
    against the same cursor.  Over time, these internal DDF control
    blocks accumulate and can lead to "short on storage" related
    symptoms, such as DB2 Storage Manager component abends
    including:
     . 04E-00E20003
     . 04E-00E20004
     . 04E-00E2000B
     . 04E-00E20015
     . 04E-00E20016
    When DB2 is configured with DDF THREADS=INACTIVE (DSN6FAC
    CMTSTAT INACTIVE) and the application contains statements which
    hop outbound to another server, this additional DB2 Storage
    Manager component abend can also occur:
     . 04E-00E20005
    To circumvent this problem, autocommit at the connection level
    can be turned off by the client application.  Alternatively,
    specify a queryCloseImplicit Connection or DataSource property
    with the value of QUERY_CLOSE_IMPLICIT_YES(1) or
    QUERY_CLOSE_IMPLICIT_NO(2) from the client application.
    

Problem conclusion

  • DB2 for z/OS server processing has been changed to correctly
    clean up internal DDF control blocks for WITH HOLD cursors
    during commit processing that occurs implicitly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK94943

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-28

  • Closed date

    2009-10-19

  • Last modified date

    2011-02-15

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

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

    UK51176 UK51177

Modules/Macros

  • DSNLQDIS DSNLXCQ7 DSNLZS00
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK51176

       UP09/11/03 P F911

  • R910 PSY UK51177

       UP09/11/03 P F911

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 February 2011