Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC88621 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
10.1fp2 has the fix 
 
No memory overwrite with null terminator
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.11.2012
18.12.2012
18.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList