DB2 - Problem description
Problem IT21437 | Status: Closed |
ON ENCRYPTED DATABASES RUNNING EXTENT MOVEMENT EXTENTLATCH HELD BY PAGE CLEANER NOT RELEASED CAUSING HANG | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem 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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users with encrypted database running extent movement. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Install latest fix pack. | |
available fix packs: | |
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Db2Version 11.1 fix pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.07.2017 15.03.2018 15.03.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |