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

SQLPARAMDATAADONET SYSTEM.ACCESSVIOLATIONEXCEPTION

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
ADO.NET application get AccessViolationException as below when 
inserting LOB as array input: 
 
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.SQLParamDataADONET(IntPtr 
hStmt, IntPtr& rgbValue, Int32& iRowsAffected, Int32& 
pCursorType, Int32& pbfOutFlags) 
   at 
IBM.Data.DB2.DB2Command.StreamInputParameters(CommandBehavior 
behaviour, Boolean bBatchStmt, Boolean bIsExecNonQuery, Int32& 
iTotalRowsAffected, Int32& iCursorType, Int32& bfFlags) 
   at 
IBM.Data.DB2.DB2Command.ExecuteReaderObject(CommandBehavior 
behavior, String method, DB2CursorType reqCursorType, Boolean 
abortOnOptValueChg, Boolean skipDeleted, Boolean isResultSet, 
Int32 maxRows, Boolean skipInitialValidation) 
   at 
IBM.Data.DB2.DB2Command.ExecuteReaderObject(CommandBehavior 
behavior, String method) 
   at IBM.Data.DB2.DB2Command.ExecuteReader(CommandBehavior 
behavior) 
   at IBM.Data.DB2.DB2Command.ExecuteReader() 
   at Orcas.TestOrcas.LOBXMLSP(DB2Connection conn) in 
C:\svtwkld\OrcasAppl\TestOrcas.cs:line 1992 
   at Orcas.TestOrcas.startSelect() in 
C:\svtwkld\OrcasAppl\TestOrcas.cs:line 203 
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state, 
Boolean ignoreSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state) 
   at System.Threading.ThreadHelper.ThreadStart() 
 
After analyzing the generated core, we get below stack trace. 
This stack gets generated when db2trc was on and db2trc is 
trying to dump the corrupted source buffer: 
 
 
00000000`3eb4cdf8 00000000`1d4b0cd3 
DB2OSSE64!_intel_new_memcpy+0x13d4 
00000000`3eb4ce00 00000000`1cec40d6 DB2OSSE64!_gtraceVar+0x1cd 
[gtrace.C @ 2630] 
00000000`3eb4ced0 00000001`8030b3d5 db2sys64!pdtData10+0x23a 
[pdtraceapi.C @ 811] 
00000000`3eb4d020 00000001`801fc33e 
db2app64!CLI_callbDrdaInputLob+0x2237 
[E:\db2_v97fp8\ntx64\s130316\engn\cli\clibindin.skl @ 1854]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ADO.NET application user.                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp4 or later releases.                    * 
****************************************************************
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
db2_v101fp4 contains fix of this issue.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.02.2014
26.07.2016
26.07.2016
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