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 IC88621 Status: Closed

MEMORY OVERWRITE WITH NULL TERMINATOR IN CLIENTBODATETOCHAR WHEN NTS
ENVIRONMENT ATTRIBUTE IS SET TO FALSE AND DATETIMESTRINGFOR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Memory overwrite with null terminator in clientboDateToChar when 
NTS environment attribute is set to false and 
DateTimeStringFormat is set to EUR in db2cli.ini
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* when NTS environment attribute is set to false and           * 
* DateTimeStringFormat is set to EUR in db2cli.ini             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* customer can move to 101.fp2                                 * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
10.1fp2 has the fix 
 
No memory overwrite with null terminator
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.11.2012
18.12.2012
18.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList