DB2 FOR LUW / DB2FORLUW / 910 - DB2

The DB2 instance may trap (SIGSEGV) in sqlplGetLockWaitInfo() 
function when an application snapshot is obtained and the tpmon 
interface API is used. 
 
This happens only when the application code uses the sqleseti() 
API to set DB2 client information to pass accounting information 
to the DB2 Server. DB2 may corrupt memory on the stack, if the 
string that it passed by the "tpmon_acc_str" element is long 
enough to exceed the allowed internal maximum size (255 byte). 
In addition for this to happen the codepage setting of the 
client and server must be different, so that codepage conversion 
happens internally. 
 
A typical trap file may show the following stack trace: 
 
sqlplGetLockWaitInfo 
sqm_snap_appl 
sqlmonssagnt 
sqlmonssbackend 
sqlesrvr 
sqleMappingFnServer 
sqlerKnownProcedure 
sqlerCallDL 
sqljs_ddm_excsqlstt 
sqljsParseRdbAccessed 
sqljsParse 
...

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 12.                      * 
****************************************************************

First fixed in DB2 Version 9.1 Fix Pack 12.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC80625 IC80626 IC80627 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

02.01.2012
02.08.2012
02.08.2012

9.1.FP12