IBM Support

IT21437: ON ENCRYPTED DATABASES RUNNING EXTENT MOVEMENT EXTENTLATCH HELD BY PAGE CLEANER NOT RELEASED CAUSING HANG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After IT20923 it is possible that a database with native
    encryption running extent movement could leak latches and
    potentially cause Db2 to
    hang. Examples of extent movement commands are "ALTER TABLESPACE
    <tsname> [REDUCE MAX|LOWER HIGH WATER MARK]". The following
    message in db2diag.log indicates that
    latches for extent movement have been leaked:
    
    2017-07-14-09.34.17.875192-240 E131386E457           LEVEL:
    Severe
    PID     : 20985                TID : 139700773840640 PROC :
    db2sysc
    INSTANCE:                      NODE : 000
    HOSTNAME:
    EDUID   : 229                  EDUNAME: db2pclnr (ENCDB)
    FUNCTION: DB2 UDB, oper system services,
    sqloDumpLatchTableToLog, probe:10
    DATA #1 : String, 98 bytes
    Latch leaked on EDU termination: File sqlbExtentMovement.C :
    Line 464 (Identity: 297) HoldCount: 2
    
    Latch leaking is possible due to a timing hole. The probability
    of having a hang increases as concurrent workloads with extent
    movement get heavier.
    

Local fix

  • Install latest fix pack.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users with encrypted database running extent movement.   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to the latest fix pack.                              *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Db2Version 11.1 fix pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21437

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-13

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 March 2018