|
Problem IC62125
|
Status: Closed |
Multi-threaded non-Java application either crashes or has code page conversion issues such as truncation of data |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW v9.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* A multi-threaded non-Java application, or a Java *
* applicationusing the legacy JDBC type 2 driver, may crash or *
* hang withanaccess violation error (for example, C0000005 *
* exception onWindows). This can alsoreport a code page *
* conversion problem (such as datatruncation)when connecting *
* or processing the data sent by the server.Another symptom of *
* this problem would be incorrect code pageconversion with no *
* errors reported. The problem occursbecausethe code page *
* conversion cache is not used in a thread safeway.An example *
* of a failing stack due to an access violation *
* isthefollowing:Component Prog ID: 1[ODBC][Env 3851978]Method *
* Name: IDispenserDriver::CreateResourceProcess Name: *
* DataSvrRemote.Net.exeException: C0000005Address: *
* 0x03BEF6F8Call Stack:DB2G11N!sqlnlsschr + *
* 0x8b4DB2G11N!sqlnlscpcv + 0x2101DB2G11N!sqlnlscpcv + *
* 0xa09DB2G11N!sqlnlscpcv + 0x3b0DB2SYS!sqlocpcv + *
* 0xa5DB2APP!CLI_utlGetBindFiles + *
* 0x27cDB2APP!CLI_utlGetBindFiles + 0x246cDB2APP!SQLGetInfo + *
* 0x53aDB2APP!SQLGetInfoW@20 + 0x4ebodbc32!SQLRowCount + *
* 0xd0codbc32!SQLRowCount + 0xe27odbc32!SQLConnectA + *
* 0x1006comsvcs!DispManGetContext + *
* 0x9ebcomsvcs!DispManGetContext + 0x1f41odbc32!SQLConnectA + *
* 0x1813odbc32!SQLConnectA + 0x1976odbc32!SQLConnectA + *
* 0x2882odbc32!SQLSetEnvAttr + 0x2f1d+ 0x37b05af+ 0x865e4d+ *
* 0x865bbAn example of data truncation error during connect is *
* whenthe.Net provider encounters multiple CLI0106E *
* "connectionclosed"errors due to code page conversion *
* problems when convertingtheconnection string.The following *
* error may also be observed:[IM001] [Microsoft][ODBC Driver *
* Manager] Driver does notsupportthis function. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW v9.5 Fixpak 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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 |
First fixed in DB2 LUW v9.5 Fixpak 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC62126
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.07.2009
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
