DB2 FOR LUW / DB2FORLUW / A10 - DB2

Set write suspend/resume may deadlatch if it is not able to 
access the db config file. 
 
The following message will be seen in the db2diag.log 
 
2014-05-27-15.09.56.282687-240 I332308A2711         LEVEL: 
Warning 
PID     : 6946998              TID : 249034         PROC : 
db2sysc 0 
INSTANCE: db2prd               NODE : 000           DB   : PRD 
APPHDL  : 0-2339               APPID: *LOCAL.db2prd.140527191028 
AUTHID  : DB2PRD               HOSTNAME: wbaurp10 
EDUID   : 249034               EDUNAME: db2agent (PRD) 0 
FUNCTION: DB2 UDB, config/install, sqlf_read_db_and_verify, 
probe:878 
DATA #1 : <preformatted> 
Error on sqlf_openfile. 
pDbName: <NO DBNAME> 
pCfgFilePath 
/db2/PRD/db2prd/NODE0000/SQL00001/MEMBER0000/SQLDBCONF 
pMemberDbPath /db2/PRD/db2prd/NODE0000/SQL00001/MEMBER0000/ 
memberCfgFilepath 
/db2/PRD/db2prd/NODE0000/SQL00001/MEMBER0000/SQLDBCONF 
bool bGlobalFile 0 
globalDbPath /db2/PRD/db2prd/NODE0000/SQL00001/ 
globalCfgFilepath /db2/PRD/db2prd/NODE0000/SQL00001/SQLDBCONF 
userExpectedSize 0 
pFileOpen 0 
openMode 76 
callerID 405929991 
retry: 0 of num_retries: 0 
rc: -2029060074 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
&#160; [0] 0x090000000F6AABB4 pdLogPrintf + 0x60 
&#160; [1] 0x090000000F9A0478 
sqlf_read_db_and_verify__FPcN21bP10sqlf_dbcfdsUlP12SQLO_FHANDLEP 
iiT10_P5sqlca + 0xC0C 
&#160; [2] 0x090000000FC75E38 
sqlfIntUpdateDbCfg__FPCcN21P6db2CfgP5sqlca + 0x42C 
&#160; [3] 0x09000000116EBA18 
writeNew__28sqeGlobalSuspendIOStateLotchFv + 0x1A4 
&#160; [4] 0x09000000116E3100 release__22@82@13520@sqlpValLotchFb + 
0x3B8 
&#160; [5] 0x0900000010188154 
sqleSetWriteResume__FP5sqlcaP9sqeBsuEduCUl + 0x25EC 
&#160; [6] 0x09000000101AD40C 
sqleTriggerSuspendIO__FP14db2UCinterfaceP5sqldaT2P5sqlca + 0x554 
&#160; [7] 0x090000000FC10524 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x8F0 
&#160; [8] 0x090000000FD8993C 
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x960 
&#160; [9] 0x09000000116B6404 
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x1694 
&#160; [10] 0x090000000FD73014 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x7C 
&#160; [11] 0x090000000FF15490 
.sqljsParse.fdpr.clone.1761__FP13sqljsDrdaAsCbP14db2UCinterfaceP 
8sqeAgentb + 0x37C 
&#160; [12] 0x090000000F84E574 
@73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x2A0 
&#160; [13] 0x090000000FE64B94 
@73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x1FC 
&#160; [14] 0x090000000FE654A4 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x558 
&#160; [15] 0x090000000FE64718 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x21C 
&#160; [16] 0x090000000FA8EA94 RunEDU__8sqeAgentFv + 0x59C 
&#160; [17] 0x090000000FA8DD28 EDUDriver__9sqzEDUObjFv + 0x13C 
&#160; [18] 0x090000000FA8DBB0 sqlzRunEDU__FPcUi + 0x10 
&#160; [19] 0x090000000FA9E3C4 sqloEDUEntry + 0x264 
&#160; [20] 0x0900000000619C90 _pthread_body + 0xF0 
&#160; [21] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
Obtaining a trapfile will show the globalSuspendIOStateLotch 
being held and waited on by the same thread. 
 
<LatchInformation> 
 
Waiting on latch type: (SQLO_LT_globalSuspendIOStateLotch) - 
Address: (0x78000001f8b5640), Line: 760, File: 
../include/sqleSuspend.h 
 
Holding Latch type: (SQLO_LT_globalSuspendIOStateLotch) - 
Address: (0x78000001f8b5640), Line: 760, File: 
../include/sqleSuspend.h HoldCount: 1 
Holding Latch type: (SQLO_LT_preventSuspendIOLotch) - Address: 
(0x78000001f8b5608), Line: 5515, File: sqleSuspend.C HoldCount: 
1 
</LatchInformation>

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 5                               * 
****************************************************************

First fixed in DB2 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

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

03.06.2014
17.02.2017
17.02.2017