home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC79776 Status: Closed

MEMORY LEAK WAS OCCURRED VIA NSE.

product:
DB2 NET SEARCH / 5765F3802 / 950 - DB2
Problem description:
An NSE query that fails with CTE0118 error. 
512 bytes memory block allocated by Getctype() is leaking 
memory. 
 
Here is a part of stack strace. 
 
ntdll!LdrGetProcedureAddress+00014780 
MSVCR80!malloc+00000151 
MSVCR80!calloc_crt+0000003E 
MSVCP80!Getctype+0000002D 
CTEITL20!ItlClDix::obtainDocNameFix+000028E3 
CTEITL20!itlHandleNewErrorInfo+0000087E 
cteue!CteTextSearch_BE1+00000B90
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of NSE Search Function                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Problem is fix in db2 Net Search Extender v95 Fix Pack 9.    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem is fix in db2 Net Search Extender v95 Fix Pack 9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79833 IC84153 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.11.2011
17.04.2012
17.04.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList