DB2 - Problembeschreibung
Problem IT06378 | Status: Geschlossen |
MEMORY LEAK IN GEO-SPATIAL CALLS WHILE ACCESSING SPECIFIC TYPE OF DATA | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
There is a memory leak which are triggered by Geo-spatial function calls such as st_intersects() when run on specific types of data. 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 -memb pid=<db2sysc pid> will show OSSe blocks allocated with LOC 43 or 60 and File 0. A snippet of the output from db2pd -memb 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 0 .. .. Total set size: 880888 bytes Memory blocks sorted by size: PoolID PoolName TotalSize(Bytes) TotalCount LOC File OSSe OSSe 880888 2723 43 0 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 FP11 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Fixed in DB2 v9.7 FP11 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.01.2015 13.10.2015 13.10.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP11 | |
Problem behoben lt. FixList in der Version | |
9.7.0.11 |