DB2 FOR LUW / DB2FORLUW / B50 - DB2

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

truncate the db2diag.log and/or notify log file (.nfy)

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.06.2021
16.06.2021
21.06.2021