DB2 FOR LUW / DB2FORLUW / B10 - DB2

db2ReadLog API can cause memory leak in dbhaep (dbh) if the API
receives an error to find a log extent which contains given LSN.
Users observe the following memory blocks keep increasing if
he/she is hitting this problem. The file hash number
(1615387857) and line of code (1565) represents the leaking
point.

$ db2pd -db DBNAME -memblock 2 sort

PoolID  PoolName  TotalSize(Bytes)  TotalCount LOC   File
2       dbh       47095200          130820     1565  1615387857

db2flsn command can be used to see if db2ReadLog will receive an
error to find a log extent.
For example:

1. Login to the databade server as non-instance user.
2. Run the following commands.

$ . /sqllib/db2profile
$ db2flsn -q -db DBNAME 
$ db2diag -g function:=sqlpScanHistFileForRecoveryList

2017-01-04-14.17.14.508961+540 I89455A443       LEVEL: Error
PID     : 25362920             TID : 1          PROC : db2flsn
INSTANCE: db2inst1             NODE : 000
HOSTNAME: host01
EDUID   : 1
FUNCTION: DB2 UDB, data protection services,
sqlpScanHistFileForRecoveryList, probe:3900
MESSAGE : Error in sqlpScanHistFileForRecoveryList, rc
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF10D0 : FFFF F78D

****************************************************************
* USERS AFFECTED:                                              *
* Users who use db2ReadLog API.                                *
* Replication solutions like SQL replication, Q replication    *
* and CDC use the API.                                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Please upgrade to DB2 V11.1 Mod2 FixPack2 or later.          *
****************************************************************

Please eliminate the error to find the log file.
For example, users can take a database backup to eliminate FFFF
F78D (SQL2163N).

not known / see Local fix

forerunner  : IT18651 
follow-up : 

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

04.08.2017
10.10.2017
10.10.2017