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

DB2 INSTANCE CRASHES IN DB2 DEADLOCK EVENT MONITOR IN THE
SQLNPMASKPASSWORD FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The Db2 instance may hit SIGSEGV (signal 11) with following
stacktrace:



DB2 build information: DB2 v11.1.4.4 special_38396 SQL11014
timestamp: 1601620491.106298000
timezone : 36000
convert : echo `perl -MPOSIX -le 'print strftime
"%Y-%m-%d-%H.%M.%S",gmtime(1601656491)'`.106298000 +1000
instance name: db2inst1.000
EDU name : db2agent (SAMPLE) 0 [-]
EDU ID : 75821
Signal #11
uname: S:AIX R:1 V:7 M:00FA46304C00 N:dj2102p-dbsa001
process id: 50397756
parent process id: 63439304
thread id : 75821 (0x1282D)
kthread id : 132383423



0000000B 00000000 00000032 00000000
00000000 00000000 0A00031D 30000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000

Signal #11 (SIGSEGV): si_addr is 0x0A00031D30000000, si_code is
0x00000032 (SEGV_MAPERR:Address not mapped to object.)




-------Frame------ ------Function + Offset------
0x090000002C86C0C8 sqlnls_CharWidth2 + 0x3C8
0x090000004175C4DC sqlnpMaskPassword__FCPcCPUlCUiCb + 0x1DC
0x09000000429519F0
gen_dlconn_events__15sqm_dlconn_listFPC8sqeAgentP8SQLP_LRB +
0x1210
0x090000004114E4B4
sqlplWaitOnWP__FCP9sqeBsuEduCP14SQLP_LOCK_INFOCP8SQLP_LRBCP15SQL
P_LTRN_CHAINCbN25 + 0x22B4
0x090000004806520C
sqlplMakeNewRequestNonSD__FP9sqeBsuEduP14SQLP_LOCK_INFOP11SQLP_T
ENTRYP8SQLP_LRBT4P15SQLP_LTRN_CHAINbT7Cb + 0x1AAC
0x0900000041473870
sqlpUpgradeLock__FP9sqeBsuEduP14SQLP_LOCK_INFO + 0x1870
0x09000000420BC554 sqldEscalateLocks__FP8sqeAgenti + 0xD54
0x0900000041ABECB8
sqldLockTable__FP8sqeAgentP14SQLP_LOCK_INFOUiUsi + 0xF78
0x090000004210402C
sqldScanOpen__FP8sqeAgentP14SQLD_SCANINFO1P14SQLD_SCANINFO2PPv +
0x5EC
0x090000004374F9C4 sqlriopn__FP8sqlrr_cbP9sqlri_taoPi + 0xD84
0x09000000474B57E0 sqlriNljnNonPiped__FP8sqlrr_cb + 0x3E0
0x0900000043B3B95C
sqlriExecThreadFunc__FP8sqlrr_cbP12sqlri_opparmPl + 0x5C
0x0900000043B3B268 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x648
0x0900000042BB15C4 sqlrr_process_execute_request__FP8sqlrr_cbib
+ 0x3624
0x0900000042B4B720 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo
+ 0x4A0
0x090000004527926C executeSection__10pvmPackageFP5sqlcaUib +
0x98C
0x0900000045274228 executeQuery__3PVMFUib + 0x208
0x0900000045280EE0 run__3PVMFv + 0xFE0
0x090000004526CB5C pvm_entry + 0x45C
0x0900000040A8CA8C sqloInvokeFnArgs + 0x5D6C
0x0900000044439718
IPRA.$sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorInt
fb + 0x2AF8
0x090000004442F468 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x2008
0x0900000044430370 sqlricall__FP8sqlrr_cb + 0x670
0x0900000043B3B238 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x618
0x0900000042BB15C4 sqlrr_process_execute_request__FP8sqlrr_cbib
+ 0x3624
0x0900000042B4B720 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo
+ 0x4A0
0x0900000047F766BC
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x5BC
0x0900000047EF2CE0
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x280
0x0900000047EF5D64
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x2264
0x0900000047EC0F3C
IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C
0x0900000047EC9654
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4
0x0900000047EBEFF0
IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13F0
0x0900000047EBC434 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
0x334
0x0900000040BE49A0 RunEDU__8sqeAgentFv + 0xB60
0x0900000040BBEBC0 EDUDriver__9sqzEDUObjFv + 0x300
0x0900000040AA0200 sqloEDUEntry + 0x360


This is due to a db2 deadlock event monitor capturing a static
sql statement which contains sensitive information (e.g.
passwords) which must be masked. The error may occur if the
large value is being masked.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6 or later                                   *
****************************************************************
Local Fix:
Disable any db2 deadlock event monitors.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6 or later                                   *
****************************************************************
Comment
Upgrade to 11.5.6 or later
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.10.2020
21.06.2021
21.06.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)