|
Problem IC84419
|
Status: Closed |
EMBEDDED SQL APPLICATION MAY CRASH WHEN USING MULTIPLE CURSORS WITH LOB OR XML COLUMNS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Embedded SQL applications that have multiple cursors open to
select varying numbers of LOB or XML columns could crash when
closing the cursors or if there are still open cursors, at
application exit.
Stack traces will be similar to:
...
<signal/exception>
csmUnmarkCDB
csmFreeLobCDB
csmClearDataInfoList
csmFreeCCB
csmClose
sqlacall
...
Or:
...
<signal/exception>
csmClearDataInfoList. (or csmFreeCCB)
csmCursorBlaster
sqleUCdisconnect
sqleUCtermAllCtx
sqleterm
sqle_ctx_exit_function
sqle_myexitlist_function
sqleExitApplicationEnvironment
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fixpack 1 *
**************************************************************** |
| Local Fix: |
Opening the cursor with the largest number of LOB/XML columns
first may avoid the problem.
Temporarily, if the application logic allows, stop closing
cursors and set the registry variable DB2NOEXITLIST=YES to avoid
the application side cursor tear-down. Use the command "db2set
DB2NOEXITLIST=YES" |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
|
| Solution |
First fixed in DB2 V10.1 Fixpack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
07.11.2012
07.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
