DB2 FOR LUW / DB2FORLUW / 970 - DB2

If extent movement is in the middle of reducing containers, and 
if db2stop force, or alter tablespace reduce stop is issued, DB2 
will attempt to interrupt extent movement.  However, due to this 
problem the extent movement will not be able to receive the 
interrupt request, causing DB2 to hang. 
 
When this happens the extent movement thread will be showing the 
following stacks: 
 
_syscall(0xfffffffeef3c0840,0xfffffffea57fa7ac,0xfffffffeef3c084 
4,0xfffffffea57fa4b0,0x1,0xfffffffea57fa4a8) 
+ 0x70 
##### Object: /vbs/engn/lib/libdb2e.so.1 
__1cIsqeAgentOIntrptWaitLock6MpnQSQdDLO_EDUWAITPOST_ipIi_i_(0x20 
1210080,0xfffffffeef3c0840,0x64,0x0,0xffffffff7cf84f48,0xfffffff 
f870f00b9) 
+ 0x464 
__1cIsqlplnfd6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO_pnISQdDLP_LCB_pn 
JSQdDLP_LHSH_pnISQdDLP_LRB_IiLipnISQdDLP_AWB_i_i_(0x0,0xfffffffe 
ef3c0840,0x0,0xfffffffec1726f30,0xfffffffec273e500,0xffffffff7cf 
84f48) 
+ 0x1670 
__1cIsqlplhed6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO_pnISQdDLP_LCB_pn 
ISQdDLP_AWB_pnJSQdDLP_LHSH_pnISQdDLP_LRB_IiL_i_(0x201210080,0xff 
fffffea57fc0f8,0xfffffffec1780080,0xfffffffeef3c0838,0xfffffffec 
180cd00,0xfffffffec2398880) 
+ 0x1d4 
__1cHsqlplrq6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO__i_(0x3842,0xffff 
fffea57fc0f8,0xffffffff7c002150,0xfffffffeef3c0820,0xfffffffec17 
80080,0x0) 
+ 0x704 
__1cWsqlbEMReduceContainers6FpnMSQdDLB_POOL_CB_IpnJsqeBsuEdu__i_ 
(0xfffffffe00000000,0x20107dbf4,0x201210080,0x0,0x74,0x0) 
+ 0x2e8 
__1cWsqlbLockAndMoveExtents6FpnMSQdDLB_POOL_CB_bIpnJsqeBsuEdu__i 
_(0x1,0xfffffffea57fc4f0,0x3fffff,0x201210080,0xffffffff0dad90a0 
,0x1000) 
+ 0x784 
__1cbCsqlbExtentMovementEntryPoint6FpnJsqeBsuEdu_pv_v_(0x2012100 
80,0xfffffffef640a200,0x11,0xffffffff0dad90a0,0x1408,0x2) 
+ 0xd8 
__1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x15d0,0x20121 
0080,0x0,0x20000,0xffffffff7d62a908,0xffffffff7cf84f48) 
+ 0xf94 
__1cIsqeAgentGRunEDU6M_v_(0x201210080,0x201211590,0x18280400,0xf 
fffffff7c002150,0xffffffff7d62a8e0,0x7258) 
+ 0x72c 
 
while the agent attempting to interrupt the extent movement 
agent will be showing the following stacks: 
 
_syscall(0xffffffff0dada4b0,0xfffffffeab3e5814,0xffffffff0dada4b 
4,0x0,0x1,0xfffffffeab3e5618) 
+ 0x70 
##### Object: /vbs/engn/lib/libdb2e.so.1 
__1cbHsqlbTerminateExtentMovementIcoord6FHpnJsqeBsuEdu__i_(0x11, 
0xffffffff7af67e1c,0x0,0xffffffff44361300,0x1400,0xffffffff7c002 
150) 
+ 0x3a4 
__1cNsqlbAlterPool6FHpnbASQdDLB_TABLESPACE_ATTRIBUTES_IpnMSQdDLB 
_GLOBALS__i_(0x2,0x2,0x0,0xffffffff44361300,0x0,0x4000) 
+ 0x9b0 
__1cNsqldPoolAlter6FpnIsqeAgent_HpnbASQdDLB_TABLESPACE_ATTRIBUTE 
S__i_(0x201215da0,0x20112dbf4,0xfffffffeab3ec158,0x5e34,0xff,0xf 
fffffff7cf84f48) 
+ 0x38c 
__1cKsqlrldpalt6FpnIsqlrr_cb_pChpciipnIsqlr_tid_L22pnTsqlrl_tbsp 
ace_parms__i_(0x1000,0x0,0xffffffffffffffff,0x0,0x1b600000,0x11) 
+ 0xa40

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If extent movement is in the middle of reducing containers,  * 
* and if db2stop force, or alter tablespace reduce stop is     * 
* issued, DB2 will attempt to interrupt extent movement.       * 
* However, due to this problem the extent movement will not be * 
* able to receive the interrupt request, causing DB2 to hang.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* On current release, avoid running ALTER TABLESPACE REDUCE    * 
* MAX or ALTER TABLESPACE LOWER HIGH WATER MARK that           * 
* might trigger extent movement; or when extent movement is in * 
* progress, do not attempt to run DB2STOP FORCE or ALTER       * 
* TABLESPACE REDUCE STOP.                                      * 
* Upgrade to DB2 Version 9.7 fix pack 3 or higher.             * 
****************************************************************

Kill db2 and restart the instance

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First Fixed in DB2 Version 9.7 fix pack 3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.07.2010
23.09.2010
10.12.2010

9.1.FP7,
9.7.FP3