|
Problem IC83790
|
Status: Closed |
MEMORY LEAK IN CREATING GEODETIC INDEX |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When using Geodetic library and running inserts/updates many
values which update the geodetic (spatial) index, there is
possibility of a major memory leak, which will affect the
performance of the machine and database.
The output of db2pd -memb will show OSSe pools with File 0
having a very big memory allocation or continuously growing
without being released.
Example:
Memory blocks sorted by size:
PoolID PoolName TotalSize(Bytes) TotalCount LOC File
OSSe OSSe 2064469528 204131 43 0
OSSe OSSe 6815640 104 4293
745254192
OSSe OSSe 3801088 29 4512
925998910
OSSe OSSe 3705064 71 128
1235720678 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* This is due to the allocation of memory for geodetic control *
* blocks during the TF_FIRST call to gseGridIndexKeyGenerator. *
* The memory is released during the TF_FINAL call to *
* gseGridIndexKeyGenerator but this call is never made even *
* though the UDF is defined WITH FINAL CALL. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 and Fix Pack 7 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.7 and Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.05.2012
25.10.2012
25.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
