IBM Support

PH39571: ABEND04E 00C90101 DSNILKDB ERQUAL1001 1001 ON A LOCK CHANGE REQUEST

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND04E RC00C90101 DSNILKDB ERQUAL1001 on a lock CHANGE
    request for a workfile DBD lock.  The error occurs due to
    a bad from duration.
    LKTR:
    500 chge dbd  none comm 0447.0000.00000000 fromdura DSNILKDB
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users that use                           *
    * declare global temporary table                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABEND=04E-RC00C90101 DSNILKDB                                *
    * with ERQUAL1001 during commit.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    When the applications use the declared global temporary table
    to perform SQL queries, DB2 will dedicate a workfile database
    to hold the declared global temporary table and lock the work
    file database with allocation duration DBD lock and remember
    the lock duration information in the internal thread-level
    database descriptor control block. Under some situations, the
    allocation duration lock could be released at commit time. The
    corresponding internal control block will be freed at the same
    time. However, due to an erroneous condition checking, the
    allocation duration DBD lock was not released at commit time
    but the internal control block was freed. When the next SQL
    query, which also used the work file database performs the
    commit, the newly created internal control block lock duration
    information is out of sync with the IRLM remembered previous
    DBD lock duration. Because of this out of sync information, DB2
    abended in DSNILKDB with ERQUAL1001.
    

Problem conclusion

  • Fixes made in Db2 to correctly handle the internal condition
    checking for DBD lock during the commit process.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH39571

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-04

  • Closed date

    2022-01-19

  • Last modified date

    2022-02-01

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

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

    UI78975

Modules/Macros

  • DSNICMT2 DSNIBCTD
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI78975

       UP22/01/27 P F201

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.

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

Document Information

Modified date:
02 February 2022