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 IT35444 Status: Closed

MULTIPLE MEMORY LEAKS IN GEO-SPATIAL CALLS WHEN EXECUTING CERTAIN
GEO-SPATIAL FUNCTIONS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
There are multiple a memory leaks which are triggered by
Geo-spatial function calls.

1. Starting in V11.5GA and later using Spatial Extender and
Spatial Analytics functions ST_LOCATEALONG, ST_LOCATEBETWEEN,
ST_FINDMEASURE, ST_MEASUREBETWEEN and ST_BUFFER may result in
memory leaks when executed.

2. Starting in V11.5.5 using Spatial Analytics functions (in
addition to the first issue) a memory leak occurs when executing
any spatial ST_* function requiring a coordinate system for
processing, e.g. any of the spatial relation functions such as
ST_INTERSECTS.


The symptoms are shown in:

a) top output ( The RES - SHR value for db2sysc would be
unusually large )
OR
b) ps -elf output will show an unusually large size for the
db2sysc pid and it will slowly keep growing
AND
c) db2pd -memblocks pid= will show OSSe blocks
allocated with LOC 43 and File 0.

A snippet of the output from db2pd -memblocks output:

Address            DataAddress        PoolID     PoolName BlkAge
Size(Bytes)  I LOC   File
0x00002AABEE9008E0 0x00002AABEE9008F0 OSSe       OSSe OSSe
304          1 43         0
0x00002AABEE900A40 0x00002AABEE900A50 OSSe       OSSe OSSe
296          1 43         0
0x00002AABEE900B90 0x00002AABEE900BA0 OSSe       OSSe OSSe
296          1 43         0
0x00002AABEE900CE0 0x00002AABEE900CF0 OSSe       OSSe OSSe
320          1 43         0
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.1 or higher                            *
****************************************************************
Local Fix:
The fix is included in V11.5.5.1 and later.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.1 or higher                            *
****************************************************************
Comment
Upgrade to Db2 11.5.5.1 or higher
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.01.2021
31.03.2021
31.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)