|
Problem IC80624
|
Status: Closed |
DB2 INSTANCE MAY TRAP IN SQLPLGETLOCKWAITINFO() WHEN RUNNING APPLICATION SNAPSHOT |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
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
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 12. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 9.1 Fix Pack 12. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC80625 IC80626 IC80627
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.01.2012
02.08.2012
02.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP12
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.12
|
 |
