home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC62126 Status: Geschlossen

Multi-threaded non-Java application either crashes or has code page
conversion issues such as truncation of data

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A multi-threaded non-Java application, or a Java application 
using the legacy JDBC type 2 driver, may crash or hang with an 
access violation error (for example, C0000005 exception on 
Windows). This can also 
report a code page conversion problem (such as data truncation) 
when connecting or processing the data sent by the server. 
 
Another symptom of this problem would be incorrect code page 
conversion with no errors reported. The problem occurs because 
the code page conversion cache is not used in a thread safe way. 
 
 
An example of a failing stack due to an access violation is the 
following: 
 
Component Prog ID: 1[ODBC][Env 3851978] 
Method Name: IDispenserDriver::CreateResource 
Process Name: DataSvrRemote.Net.exe 
Exception: C0000005 
Address: 0x03BEF6F8 
Call Stack: 
DB2G11N!sqlnlsschr + 0x8b4 
DB2G11N!sqlnlscpcv + 0x2101 
DB2G11N!sqlnlscpcv + 0xa09 
DB2G11N!sqlnlscpcv + 0x3b0 
DB2SYS!sqlocpcv + 0xa5 
DB2APP!CLI_utlGetBindFiles + 0x27c 
DB2APP!CLI_utlGetBindFiles + 0x246c 
DB2APP!SQLGetInfo + 0x53a 
DB2APP!SQLGetInfoW@20 + 0x4eb 
odbc32!SQLRowCount + 0xd0c 
odbc32!SQLRowCount + 0xe27 
odbc32!SQLConnectA + 0x1006 
comsvcs!DispManGetContext + 0x9eb 
comsvcs!DispManGetContext + 0x1f41 
odbc32!SQLConnectA + 0x1813 
odbc32!SQLConnectA + 0x1976 
odbc32!SQLConnectA + 0x2882 
odbc32!SQLSetEnvAttr + 0x2f1d 
+ 0x37b05af 
+ 0x865e4d 
+ 0x865bb 
 
An example of data truncation error during connect is when the 
.Net provider encounters multiple CLI0106E "connection closed" 
errors due to code page conversion problems when converting the 
connection string. 
 
The following error may also be observed: 
[IM001] [Microsoft][ODBC Driver Manager] Driver does not support 
this function.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW v9.7                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Multi-threaded non-Java application either crashes or        * 
* hascodepage conversion issues such as truncation of data     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpak 2                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 LUW v9.7 Fixpak 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.07.2009
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList