DB2 - Problem description
Problem IC76856 | Status: Closed |
DB2STOP FORCE HANGS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
If the user has created a partitioned multi-dimensional clustering tables in DB2 9.7 FP1 or DB2 9.7 FP2, then may be exposed to this problem. The problem occurs after performing rollout deletes from such a table. If a db2stop force is then issued while the self-tuning memory manager is reducing the size of the bufferpool, then db2stop force may hang. The stack for the self tuning memory manager will look something like this: <StackTrace> ##### Object: /lib/sparcv9/libc.so.1 _syscall(0xfffffffee177e538,0xfffffffec6bfb7e4,0xfffffffee177e53 c,0x0,0x1,0xfffffffec6bfb5e8) + 0x70 ##### Object: /view/db2_v97fp3_sun64_s100714/vbs/engn/lib/libdb2e.so.1 __1cbAsqlbDecreaseBufferpoolSize6FpnPSQdDLB_BufferPool_pnVSQdDLB _BP_UC_ALTER_INFO_pnMSQdDLB_GLOBALS__v_(0xfffffffec6bfff30,0x __1cUsqlbResizeBufferPool6FpnPSQdDLB_BufferPool_pnVSQdDLB_BP_UC_ ALTER_INFO_pnMSQdDLB_GLOBALS__i_(0xfffffffee177e340,0xfffffff __1cbCsqlbAlterAutomaticBufferPool6FIipnIsqeAgent__i_(0x58e,0x0, 0x202865da0,0x58e,0x0,0xffffffff7af6e23d) + 0x384 __1cYsqlrlStmmAlterBufferPool6FpnIsqeAgent_pciipnOdb2UCinterface _pnFsqlca__i_(0x202865da0,0xffffffff6109bf10,0xb4c68,0x0,0xff __1cTstmmAlterBufferPool6FpnIsqeAgent_pcii_i_(0x202865da0,0xffff ffff6109bf10,0x3,0x58e,0x0,0x0) + 0x1bc __1cbIstmmResizeEntriesAndRemoveFromList6FppnVstmmCostBenefitRec ord_pnQsqeLocalDatabase__i_(0xfffffffec6bfc770,0x2006fa000,0x __1cOstmmTuneMemory6FppnVstmmCostBenefitRecord_pnQsqeLocalDataba se__i_(0xfffffffec6bfc770,0x2006fa000,0xfffffffec6bfc5c0,0x0, stmmMemoryTunerMain(0x2006fa000,0x0,0xaa000,0x1,0x0,0xffffffff7b 3b71fd) + 0x30c __1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x80000051,0x2 02865da0,0x0,0x20000,0xffffffff7d63bec8,0xffffffff7cf964d0) + __1cIsqeAgentGRunEDU6M_v_(0x202865da0,0x2028672b0,0x18280400,0xf fffffff7c011068,0xffffffff7d63bea0,0x7258) + 0x72c __1cKsqlzRunEDU6FpcI_v_(0x0,0xffffffff77d63fa8,0x184dae4,0x20286 5da0,0x18d00000,0xffffffff7c88bac8) + 0xd0 sqloEDUEntry(0xfffffffec3bf4640,0xfffffffec6bfff30,0x8,0xfffffff f7d63bf18,0x18780000,0x0) + 0x3d4 ##### Object: /lib/sparcv9/libc.so.1 _thr_slot_offset(0x0,0x0,0x0,0x0,0x0,0x0) + 0x488 </StackTrace> | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * If the user has created a partitioned multi-dimensional * * clustering tables in DB2 9.7 FP1 or DB2 9.7 FP2, then may be * * exposed to this problem. The problem occurs after * * performing rollout deletes from such a table. If a db2stop * * force is then issued while the self-tuning memory manager is * * reducing the size of the bufferpool, then db2stop force may * * hang. * * * * The stack for the self tuning memory manager will look * * something like this: * * * * <StackTrace> * * * * ##### Object: * * /lib/sparcv9/libc.so.1_syscall(0xfffffffee177e538,0xfffffffec6 * + 0x70 * * * * ##### Object: * * /view/db2_v97fp3_sun64_s100714/vbs/engn/lib/libdb2e.so.1__1cbA * * * __1cUsqlbResizeBufferPool6FpnPSQdDLB_BufferPool_pnVSQdDLB_BP_U * * * __1cbCsqlbAlterAutomaticBufferPool6FIipnIsqeAgent__i_(0x58e,0x * + 0x384 * * * * __1cYsqlrlStmmAlterBufferPool6FpnIsqeAgent_pciipnOdb2UCinterfa * * * __1cTstmmAlterBufferPool6FpnIsqeAgent_pcii_i_(0x202865da0,0xff * + 0x1bc * * * * __1cbIstmmResizeEntriesAndRemoveFromList6FppnVstmmCostBenefitR * * * __1cOstmmTuneMemory6FppnVstmmCostBenefitRecord_pnQsqeLocalData * * * stmmMemoryTunerMain(0x2006fa000,0x0,0xaa000,0x1,0x0,0xffffffff * + 0x30c * * * * __1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x80000051,0 * + * * * * __1cIsqeAgentGRunEDU6M_v_(0x202865da0,0x2028672b0,0x18280400,0 * + 0x72c * * * * __1cKsqlzRunEDU6FpcI_v_(0x0,0xffffffff77d63fa8,0x184dae4,0x202 * + 0xd0 * * * * sqloEDUEntry(0xfffffffec3bf4640,0xfffffffec6bfff30,0x8,0xfffff * + 0x3d4 * * * * ##### Object: * * /lib/sparcv9/libc.so.1_thr_slot_offset(0x0,0x0,0x0,0x0,0x0,0x0 * + 0x488 * * </StackTrace> * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 FP3. * **************************************************************** | |
Local Fix: | |
Issue the killdb2 command to stop DB2. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
Solution | |
The problem was first fixed in | |
Workaround | |
Issue the killdb2 command to stop DB2. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.06.2011 08.06.2011 08.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.4 |