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

Instance crash due to stack overflow during query execution of a query with
LOB locators and parameter markers.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Instance can crash if LOB columns are involved and application 
is using more then 4400 locators for the same parameter marker. 
 
The stack traceback file created for the crash in the db2dump 
directory will show thousands of calls to the function 
sqlrimso, for example: 
.... 
0x00002B086E2B41DF _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2b3b 
0x00002B086E2B4006 _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2962 
0x00002B086E2B4006 _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2962 
0x00002B086E2B4006 _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2962 
0x00002B086E2B4006 _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2962 
0x00002B086E2B4006 _Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi 
+0x2962 
....... 
 
db2diag.log will have stack overflow message: 
   MESSAGE : ADM0502C  The DB2 instance has terminated 
abnormally.  To remedy this 
      problem, increase the AGENT_STACK_SZ DBM 
configuration parameter. 
     Contact IBM Support for further assistance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SQL using more then 4400 locators for the same               * 
* parametermarker.                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Instance crash due to stack overflow during query            * 
* executionof aquery with LOB locators and parameter markers.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* change application or install DB2 9.5 FP6a or higher.        * 
****************************************************************
Local Fix:
increase dbm cfg parameter AGENT_STACK_SZ  and recycle the 
instance or rewrite application to decrease the number of lob 
locators used.
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
Problem First Fixed in DB2 Version 9.5 Fix Pack 6a
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64093 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.09.2009
14.05.2010
06.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)