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

Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

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 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