|
Problem IT18426
|
Status: Closed |
DB2 might leak private memory if locators are used to access thedata (e.g. to fetch LOBs) |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
DB2 server might leak PRIVATE memory if applications connected
to database are using locators to access the data (e.g. to fetch
LOBs)
As the result, one will observe an increase in PRIVATE memory
usage
in MON_GET_MEMORY_POOL or in db2pd output:
$ db2pd -dbptnmem
Leaking allocation will be tracked as ones coming from file ID
2904145706 and line of code (LOC) ~1551 (LOC might differ
between fix packs) in the output from:
$ db2pd -memblocks private pid=<pid_of_db2sysc>
e.g:
Address . PoolID . Size(Bytes I LOC File
0x00007FA6E731B068 . 0 . 2960 1 1551 2904145706
0x00007FA6E731BC28 . 0 . 2960 1 1551 2904145706
0x00007FA6E731C7E8 . 0 . 2960 1 1551 2904145706
0x00007FA6E731D3A8 . 0 . 2960 1 1551 2904145706
...
NOTE: running
$ db2pd -memblocks private
will commit all private memory that DB2 has allocated, which
might result in paging if memory is overcommited - please run it
with caution or with supervision of DB2 support. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.12.2016
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
