suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT18651 Status: Closed

MEMORY LEAK IN DBHEAP IF DB2READLOG RECEIVES AN ERROR TO FIND LOG FILE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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. 
 
$ . <path_to_instance_home>/sqllib/db2profile 
$ db2flsn -q -db DBNAME <LSN_TO_BE_FOUND_IN_LOG> 
$ 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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2Readlog API.                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 9 or later.              * 
****************************************************************
Local Fix:
Please eliminate the error to find the log file. 
For example, users can take a database backup to eliminate FFFF 
F78D (SQL2163N).
Solution
This problem was first fixed in DB2 V10.5 FixPack 9.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.01.2017
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)