|
Problem IT22243
|
Status: Closed |
DB2CONNECT server may trap if CURRENT CLIENT_CORR_TOKEN is explicitly set by an application. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Once problem happens, the FODC_Trap is created.
Following stack is logged in the corresponding trap file:
ossDumpStackTraceInternal
ossDumpStackTraceV98
OSSTrapFile::dumpEx
sqlo_trce
sqloEDUCodeTrapHandler
_IO_ftrylockfile
sqljrMonParseSetClientInfoEx
sqljrDrdaArExcSqlSet
sqljs_ddm_excsqlset
sqljsParseRdbAccessed
sqljsParse
sqljsSqlam
sqljsDriveRequests
sqljsDrdaAsInnerDriver
sqljsDrdaAsDriver
sqeAgent::RunEDU
sqzEDUObj::EDUDriver
sqloEDUEntry
start_thread
clone
Problem happens due to incorrect processing in
sqljrMonParseSetClientInfoEx function |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 CONNECT *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 FP9 *
**************************************************************** |
| Local Fix: |
Set CURRENT CLIENT_CORR_TOKEN to string with non zero length |
| Solution |
First fixed in Db2 10.5 FP9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.09.2017
10.10.2017
10.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
