DB2 FOR LUW / DB2FORLUW / A10 - DB2

A runstats command can potentially hang is used with the 
UTIL_IMPACT_PRIORITY clause. There's a small timing hole which 
can make both the runstats agent and db2throt thread wait on 
each other causing a deadlock. The potential side effects are: 
 
1) Other Runstats using the same clause will also hang 
2) LIST UTILITIES command will hang 
3) A X lock can be held on the catalog cache row by the runstats 
which will cause queries requiring that table's information to 
compile wait behind that lock. 
 
The stack of the runstats thread will look like: 
 
thread_wait + 0x98 
sqloWaitEDUWaitPost + 0x284 
stopEDU__24SqlthStartStopControlEDUFv + 0xAC 
cancelAControlSubscription__22SqlthControllerManagerFCb + 0x1BC 
__dt__15SqlthJobControlFv + 0xB0 
__dt__8SqlthJobFv + 0x8C 
removeJob__15SqlthJobManagerFP8SqlthJob + 0x22C 
@97@sqlrRunstatsTerminateJobServices__FCP25sqlrr_RunstatsJobServ 
ices + 0xA0 
sqlrLocalRunstats__FP8sqlrr_cbP11sqlrrstringN22UcUsT6PP8sqlrg_pd 
iN39P16sqlrl_stats_colsPPsUiPPUsT15_dT15_T18_T6PP20sqlr_runstats 
_resultPsUlT24_N26CUiT15_lT24_P17sqlrlc_stats_infoPCUcPCcT24_ + 
0x6A8 
sqlrrsta__FP8sqlrr_cbP11sqlrrstringN22UcT5P17sqlrl_stats_parmsPC 
UcPs + 0x2C6C 
sqlrr_runstats_DA__FP5sqldaP5sqlca + 0x10D0 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0xAA0 
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x960 
.sqljs_ddm_excsqlstt.fdpr.clone.33__FP14db2UCinterfaceP13sqljDDM 
Object + 0x564 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x74 
 
The stack of the db2throt thread would look like: 
 
thread_wait + 0x98 
getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 0x2A8 
getConflict__17SQLO_SLATCH_CAS64FCUl + 0x78 
sendCommandsToThrottledJobs__22SqlthControllerManagerFCQ2_22Sqlt 
hControllerManager16JOB_COMMAND_TYPECd + 0x49C 
asyncControllerMain__22SqlthControllerManagerFv + 0x28C 
_asyncControllerMain__24SqlthStartStopControlEDUFPP22SqlthContro 
llerManager + 0x10 
sqloEDUEntry + 0x424

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP4                                     * 
****************************************************************

Workaround: 
----------------- 
Do not use the UTIL_IMPACT_PRIORITY clause for the RUNSTATS 
command.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in DB2 v10.1 FP4

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC99707 IT07519 IT09097 
Nachfolger : 

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

23.01.2014
02.06.2014
02.06.2014