|
Problem IT18115
|
Status: Closed |
MEMORY LEAK IN DB2SYSC DURING QUERIES WITH CONTAINS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In cases when the text search query contains keywords such as
CONTAINS or SCORE, we will observe leaks in db2sysc like the
following:
0x0090000000004a828 malloc_common_debugging
0x00900000000883610 _Fancy_malloc__FUl
0x00900000000884028 init_pres__FUl
0x009000000b4dd2538
_Insert__Q2_3std5_TreeXTQ2_3std12_Tmap_traitsXTQ2_7icu_3_213Uni
0x009000000b4dd070c
AddStringToConversionCache__Q3_2es4comm13GenRespRecordFQ2_7icu_
0x009000000b4de9b6c initUrls__Q3_2es4comm11RESTMessageFv
0x009000000b4de6ab4
__ct__Q3_2es4comm11RESTMessageFRCQ2_7icu_3_213UnicodeStringRQ3_
0x009000000b4dda2a8
sendAndRecvMesgOnce__Q3_2es4comm16SutterPerfClientFRQ3_2es4comm
0x009000000b4ddf398
sendAndRecvMesg__Q3_2es4comm17WhitneyRESTClientFRQ3_2es4comm13C
0x009000000932b5048
invoke__Q3_2es3api13SessionConfigCFRCQ2_7icu_3_213UnicodeString
0x009000000932cfb9c
doSearchPerf__Q3_2es3api10SearchableFRQ3_2es3api9ResultSetRQ3_2
0x009000000932cf9d4
doSearch__Q3_2es3api10SearchableFRQ3_2es3api9ResultSetRQ3_2es4u
0x009000000932d05ec
scalarSearch__Q3_2es3api10SearchableFRQ3_2es3api9ResultSetRCQ3_
0x009000000930ac408
search__Q2_3cie19CieSearchableScalarFPCcT1PCsUiPC13sqludf_vc_fb
0x009000000930a4144 CieTextSearchTF
0x009000000930d1e08 CieTextSearchTF_extern |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 10.1 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.11.2016
02.03.2017
02.03.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
