IBM Support

PI31477: -DIS DB LPL COMMAND ISSUED ABEND04E RC00E20003 AND THE ABEND WAS ISSUED REPEATEDLY UNTIL DB2 DOWN.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND04E RC00E20003 was issued because database command's
    storage pool occupied below the bar storage.
    Then ABEND04E RC00E20003 was issued repeatedly after the
    database command's completion until DB2 down.
    The problem scenario was,
    1. '-DIS DB(*) SP(*) LPL ONLY' was issued from a TSO user.
    2. The TSO user was cancelled.
    3. The -DIS DB command's storage pool occupied below the bar
       storage.
    4. ABEND04E RC00E20003 started to be issued.
    5. -DIS DB command completed.
    6. ABEND04E RC00E20003 continued to be issued.
    7. DB2 down.
    .
    -DIS DB command issued ABEND04E RC00E20003 because the system
    had too many objects to process.
    The DB command storage pool should have been freed at the
    -DIS DB command's completion, then ABEND04E RC00E20003 should
    have stopped at that point.
    But the storage pool was left because it was owned by the
    invoker(TSO user) and the invoker had been already cancelled.
    

Local fix

  • Cancel the DBCMD service task by DB2 cancel command before
    cancelling its invoker.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users, executing a                       *
    *                 DISPLAY DB(*) SP(*) LPL ONLY                 *
    *                 or                                           *
    *                 DISPLAY DB(*) SP(*) WEPR ONLY                *
    *                 command, having a large amount of objects    *
    *                 in the DB2 catalog.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: The DISPLAY DATABASE command tries to   *
    *                      iterate all databases and tablespaces,  *
    *                      searching for objects that have a LPL   *
    *                      or WEPR state associated in the DBET.   *
    *                      If the amount of databases/tablespaces  *
    *                      is large, the command consumes a        *
    *                      significant amount of storage and might *
    *                      run out of memory.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The DISPLAY DB(*) SP(*) commands normally iterate all database
    and tablespace objects from the DB2 catalog to create the
    command output messages. For some scenarios (i.e. if restricted
    to display only advisory states) it is more efficient to first
    search within the DBET for objects with a specific state and
    then to complement the found objects with information from the
    catalog. This was done only for DISPLAY DATABASE commands that
    used the RESTRICT/ADVISORY keywords until now.
    

Problem conclusion

  • If the keywords LPL ONLY or WEPR ONLY are used in conjunction
    with a DISPLAY DB(*) SP(*), we now use the optimized code path
    that first searches the DBET for objects in LPL/WEPR state
    before adding information from the catalog to it. This code
    path is considered more efficient as far less objects are
    assumed to have a LPL or WEPR state than databases or
    tablespace exist in the catalog.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI31477

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-12-12

  • Closed date

    2015-08-07

  • Last modified date

    2015-09-02

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

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

    UI30057 UI30058

Modules/Macros

  •    DSNTDDIS DSNTDMST
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI30057

       UP15/08/25 P F508 Ž

  • RB10 PSY UI30058

       UP15/08/25 P F508 Ž

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"}],"Version":"A10","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 March 2024