DB2 - Problem description
| Problem IT02772 | Status: Closed |
STANDBY CRASH ON REORG COMMAND IN FUNCTION SQLBFREEEXTENTSFOROBJECT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
1. Problem description
Standby crashes during REORG command:
From db2diag.log we can see this messages:
2014-04-14-06.01.07.771241-240 I205520069A593 LEVEL: Severe
PID : 10420228 TID : 7969 PROC : db2sysc 0
INSTANCE: duipsep NODE : 000 DB : EPPRD
APPHDL : 0-8 APPID: *LOCAL.DB2.140413213129
HOSTNAME: beth.spherion.com
EDUID : 7969 EDUNAME: db2redom (EPPRD) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbPrepare2FreeExtOnTempSMP, probe:125
DATA #1 : <preformatted>
Array boundary exceeded.
totalSmpPages: 1, smpPage: 5
sqlbGetLastInitSmpExtent(pdef): 0
pageSize: 4096, extentSize: 64, poolPage: 2844800
2014-04-14-06.01.07.779219-240 I205520663A22518 LEVEL: Severe
PID : 10420228 TID : 7969 PROC : db2sysc 0
INSTANCE: duipsep NODE : 000 DB : EPPRD
APPHDL : 0-8 APPID: *LOCAL.DB2.140413213129
HOSTNAME: beth.spherion.com
EDUID : 7969 EDUNAME: db2redom (EPPRD) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbPrepare2FreeExtOnTempSMP, probe:136
DATA #1 : String, 35 bytes
smpMapInfo, fixCB and EMP page dump
DATA #2 : Hexdump, 12 bytes
0x07000000087F7E18 : 0000 0005 0000 022C 0010 0000 .......,....
DATA #3 : Fix control block, PD_TYPE_SQLB_FIX_CB, 200 bytes
accessMethod: SQLB_POOL_RELATIVE
fixMode: 3 SQLBX | SQLBOLD
buffptr: 0x07000000d4389000
bpdPtr: 0x07000000d0c58a00
pageLsnOnXLatch: 0000000000000000
dmDebugHdl: 0
objectPageNum: 0
empDiskPageNum: 172
unfixFlags: 0
dirtyState: SQLBCLEAN
fixInfoFlags: 0
regEDUid: 0
Pagekey: {pool:1;obj:4;type:80} PPNum:172
Obj: {pool:1;obj:4;type:80} Parent={265;4}
lifeLSN: 00006DEBED85FA50
tid: 1 33258 54546
extentAnchor: 128
initEmpPages: 0
poolPage0: 192
poolflags: 6112
objectState: 10027
lastSMP: 4294967295
pageSize: 4096
extentSize: 64
bufferPoolID: 1
partialHash: 1342439425
objDescAttributes: 0
bufferPool: 0x07000000ceca14e0
pdef: 0x070000015587eda0
glob: 0x00000001105d8320
DATA #4 : Hexdump, 4096 bytes
0x07000000D4389000 : 0030 0FD0 0000 0000 0500 502A 0000 0001
.0........P*....
0x07000000D4389010 : 0000 00AC 0004 0000 0000 0000 0000 33D1
..............3.
0x07000000D4389020 : 0000 0000 0000 0000 674D EF1A 04FB 8453
........gM.....S
0x07000000D4389030 : 0000 0001 0000 0000 0000 0000 0000 01C0
................
0x07000000D4389040 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x07000000D4389050 : 0000 0000 0000 0000 002A F8C0 002A F900
.........*...*..
0x07000000D4389060 : 002A F940 002A F980 002A F9C0 002A FA00
.*.@.*...*...*..
The stack trace should be:
<StackTrace>
-------Frame------ ------Function + Offset------
0x09000000040DAC54 sqlbFreeExtentsForObject + 0xA874
0x090000000777EB84
sqlbDMSDeleteObject__FP16SQLB_OBJECT_DESCUiP12SQLB_GLOBALSb +
0x250
0x0900000003C06514
@113@sqldReorgEnsureDeletion__FP13SQLD_REORG_CBiP16SQLB_OBJECT_D
ESC + 0x2F8
0x090000000644CE3C
sqldReorgCleanup__FP13SQLD_REORG_CBiT2P9SQLP_LSN8 + 0x2EC
0x0900000007F8A414
@113@redoCleanup__FP8sqeAgentP18SQLD_REORGEVENT_LRP9SQLP_LSN8P15
SQLD_RECOV_INFO + 0x11C
0x0900000008274E9C
sqldomRedo__FP8sqeAgentP10SQLDOM_LRHP9SQLP_LSN8P15SQLD_RECOV_INF
O + 0x2B4
0x09000000082C4134
sqldmrdo__FP8sqeAgentUsP9SQLP_LSN8PcUlN35P8SQLP_TIDP15SQLD_RECOV
_INFO + 0x714
0x09000000082BF29C
sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP10SQLP_FRA
PPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x960
0x09000000082BE600
sqlprProcDPSrec__FP10SQLPR_PRCBUiP20SQLPR_PR_QUEUE_ENTRY + 0x440
0x090000000940BAC4
sqlpPRecReadLog__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb + 0x1C28
0x0900000003F889C8 sqlpParallelRecovery__FP8sqeAgentP5sqlca +
0xD28
0x0900000004360654 sqleSubCoordProcessRequest__FP8sqeAgent +
0x19C
0x0900000004BB1DF8 RunEDU__8sqeAgentFv + 0x6FC
0x0900000004BAD858 EDUDriver__9sqzEDUObjFv + 0x13C
0x0900000004BAD6E0 sqlzRunEDU__FPcUi + 0x10
0x0900000004BC0558 sqloEDUEntry + 0x264
</StackTrace> | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * NA * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
| Solution | |
Fixed in DB2 V10.1 Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.06.2014 16.07.2015 16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|