DB2 - Problem description
Problem IT35318 | Status: Closed |
LARGE PRIVATE MEMORY LEAK WHEN PD_GET_DIAG_HIST IS INTERRUPTED PROCESSING A LARGE DB2DIAG.LOG OR NOTIFY FILE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
When the PD_GET_DIAG_HIST Table Function is cancelled, private memory may be leaked. The db2diag.log will sometimes show the error below, but this is not when the leak occurs - it is just a sign that the vulnerable type of activity (cancelling PD_GET_DIAG_HIST) is present on a system. The actual memory leak occurs when the interrupt occurs *between* successive internal calls to the function below (the processing of large files is broken up into manageable portions). In this case there is no db2diag.log entry generated. FUNCTION: DB2 UDB, WLM, sqlrwGetPDDiagHist_v10fp3, probe:400 MESSAGE : ECF=0x900003FE=-1879047170=ECF_SESSION_CANCELED The session was canceled DATA #1 : String, 41 bytes Error trying to read notificationrecords. db2pd -memblocks pid= will show leaks similar to the following : Memory blocks sorted by size: PoolID PoolName TotalSize(Bytes) TotalCount LOC File 0 31457283 3 394 paNotifLogColl.C 0 49155 3 423 paNotifLogColl.C 0 34368 8 3177 paNotifLogColl.C 0 12888 3 334 paDiagLogColl.C ... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 * **************************************************************** | |
Local Fix: | |
truncate the db2diag.log and/or notify log file (.nfy) | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 * **************************************************************** | |
Comment | |
Upgrade to 11.5.6 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.12.2020 21.06.2021 21.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |