|
Problem IC76044
|
Status: Closed |
NSE doesn't free-up the memory allocated by sqloInitSecurityAttribute(). This leads to CTE0184 error. |
| product: |
DB2 NET SEARCH / 5765F3802 / 970 - DB2 |
| Problem description: |
Customer applied the special build on 3/6 and collected
umdh output every 1 hour to confirm that the problem is
fixed. The previous stack that showed leak in tempnam does not
appear anymore. However, it seems NSE is still leaking, this
time in
another place. It seems NSE is not terminating after initiating
sqloInitSecurityAttribute.
.
+ 7134c ( 88d6a0 - 81c354) abb8 allocs BackTrace4982
+ 8e1 ( abb8 - a2d7) BackTrace4982 allocations
.
ntdll!RtlAllocateHeapSlowly+00000041
ntdll!RtlAllocateHeap+00000E9F
kernel32!LocalAlloc+00000058
DB2SYS!sqloAddOrRemoveAce+00000292 (sqloSecAuth.C, 6226)
DB2SYS!sqloInitSecurityAttribute+0000025A (sqloSecAuth.C, 7101)
CTESYNC!CteShmImplement::CteShmImplement+0000033F
CTESYNC!CteSharedMemory::CteSharedMemory+0000006C
CTELM!CteLockingService::CteLockingService+000000D0
CTELM!CteGetLockingService+000000D0
CTELM!CteGetLockingServiceWithInstPath+00000014
NSE doesn't free-up the memory allocated by
sqloInitSecurityAttribute() function and this can eventually
lead to CTE0184 error.
Problem was found at the following level, 9.5 FP6 and onwards |
| Problem Summary: |
NSE does not free up memory and leads to CTE0184 error |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 |
Fix provided in V97fp5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.04.2011
21.11.2011
21.11.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
