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

DB2 DRIVER/CLIENT MAY TRAP FOR APPLICATIONS USING THE WORKLOAD BALANCING
(WLB) FEATURE.

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
The workload balancing (WLB) feature is enabled by setting the 
enableWLB parameter to true in db2dsdriver.cfg, DB2 
Driver/Client may trap in function sqljCalcSdaCDTOverridesLen or 
sqljrDrdaArCommit. 
 
The call stack on window may look like as below: 
 
STACK_TEXT: 
00000000`2590d530 00000001`80838821 : 00000000`00000001 
00000000`00000003 00000000`00000004 00000000`2590d818 : 
db2app64!sqljCalcSdaCDTOverridesLen+0x512 
00000000`2590d6a0 00000001`8078a1ed : 00000000`00000000 
00000000`00000000 00000000`00000000 00000000`00000000 : 
db2app64!sqljCalcDscLen+0x179 
00000000`2590d700 00000001`807683d5 : 00000000`250ab9f8 
00000001`00000004 00010001`012322d0 00003728`1abc9a50 : 
db2app64!sqljrGenSqlDta+0x167 
00000000`2590d810 00000001`800e088a : 00000000`00000000 
00000001`800e2e5e 00000000`00000004 00000000`00000001 : 
db2app64!sqljrDrdaArArrayInput+0x2a3 
00000000`2590d8a0 00000001`8018462f : 00000000`1ef759e0 
00000000`250abd58 00000000`000000a0 00000000`250ab9f8 : 
db2app64!CLI_sqlExecute+0xff4 
00000000`2590d9a0 00000001`800a3a29 : 00000000`00151650 
000007fe`f1fb0c2f 00000000`000000f3 00000000`00000000 : 
db2app64!SQLExecute2+0xf03 
00000000`2590dac0 000007fe`92a29d08 : 000007fe`929a2d78 
00000000`00000000 00000000`00000000 00000000`00000000 : 
db2app64!SQLExecDirectADONET+0x1963 
 
.net application reports exception with the following call 
stack: 
Unhandled Exception: System.AccessViolationException: Attempted 
to read or write 
 protected memory. This is often an indication that other memory 
is corrupt. 
   at 
IBM.Data.DB2.UnsafeNativeMethods.DB232.SQLExecDirectADONET(DB2Ex 
ecDirectPa 
rameters* pParam) 
   at IBM.Data.DB2.DB2Command.a(Boolean A_0) 
   at IBM.Data.DB2.DB2Command.b() 
   at IBM.Data.DB2.DB2Command.ExecuteNonQuery() 
 
OR 
 
STACK_TEXT: 
00000000`1f1bd2e0 00000001`800e5f8a : 000007fe`00000000 
00000000`1b898e9c 000007fe`00000003 00000000`1b898e9c : 
db2app64!sqljrDrdaArCommit+0x34e 
00000000`1f1bd3c0 00000001`801cb963 : 00000000`1ff73f40 
00000000`00000000 00000000`00000000 00000001`800817e5 : 
db2app64!CLI_sqlCommit+0x1da 
00000000`1f1bd480 00000001`801c918d : 0000a924`0a7e86a7 
00000004`00010001 00000000`00000004 00000000`1f1be5b8 : 
db2app64!SQLTransact2+0x181 
00000000`1f1bd540 000007fe`92918b96 : 00000000`028d0002 
00000000`00000017 00000000`00000000 00000000`00000000 : 
db2app64!SQLEndTran+0x367 
 
.net application reports exception with the following call 
stack: 
Unhandled Exception: System.AccessViolationException: Attempted 
to read or write 
 protected memory. This is often an indication that other memory 
is corrupt. 
   at IBM.Data.DB2.UnsafeNativeMethods.DB232.SQLEndTran(Int16 
HandleType, IntPtr 
 Handle, Int16 CompletionType) 
   at IBM.Data.DB2.DB2Transaction.Commit()
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1.4.                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to v10.1.4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.02.2014
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList