|
Problem IC77632
|
Status: Closed |
LOAD ON RANGE PARTITIONED TABLE MAY CAUSE INSTANCE CRASH DUE TO BAD PAGE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Load on range partitioned table MAY encounter bad page and crash
the instance.
To diagnose this APAR, analyze the db2diag.log. It should show
entries for load failure similar to following:
<snip>
2011-04-30-02.01.56.273959-240 I2875234A3961 LEVEL: Severe
PID : 598878 TID : 5807 PROC : db2sysc
8
INSTANCE: xxxxxxx NODE : 008 DB : xxxx
APPHDL : 0-34439 APPID: xx.x.xx.x.xxxxx.xxxxxxxxx
AUTHID : xxxxxxx
EDUID : 58 EDUNAME: db2lbm0 8
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,
probe:2
MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad"
DIA8400C A bad page was encountered.
DATA #1 : String, 64 bytes
Error encountered trying to read a page - information follows :
DATA #2 : String, 23 bytes
Page verification error
DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes
312900
DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 88 bytes
Obj: {pool:16;obj:29;type:0} Parent={16;29}
lifeLSN: 0000000000056CE9
tid: 0 0 0
extentAnchor: 297856
initEmpPages: 0
poolPage0: 297888
poolflags: 6122
objectState: 27
lastSMP: 0
pageSize: 8192
extentSize: 32
bufferPoolID: 2
partialHash: 1900706
bufferPool: 0x0700000095c08100
pdef: 0x0700000152924b80
DATA #5 : Bitmask, 4 bytes
0x00000200
DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes
pageHead: {tbspSeed:0;obj:0;type:0} PPNum:0 OPNum:0
begoff: 0
datlen: 0
pagebinx: 0
revnum: 0
pagelsn: 0000000000000000 flag: 0
future32: 0
cbits1to31: 0
cbits32to63: 0
DATA #7 : Bufferpool globals, PD_TYPE_SQLB_GLOBALS, 1256 bytes
dbcb: 0x07800000007481a0
bpcb: 0x0700000070cbfe80
ptbl: 0x0700000070d5f700
eduType: SQLB_EDU_LOADER
eduCB: 0x0700000171a20080
qryData: 0x0000000000000000
qryDataSz: 0
qryDataPos: 0
contQryData: 0x0000000000000000
contQryDataSz: 0
contQryDataPos: 0
bglobals_flags: 0
dbmon_cb: 0x070000016c4b9680
eduId: 5807
curPfQ: 4
curRemHateListCounter: 5807
debugInfo: 0x0000000000000000
pCurRecLsn: 0x0000000000000000
clnrCB: 0x0000000000000000
prefetchPriority: 0
agentPriorityWeight: 00
staticStr:
numPFRequestsHeld: 0
memAccessCount:
m_bIsInitialized: true
m_iDisabled: 2222
m_iAccessCount: 0
CALLSTCK:
[0] 0x090000001497C130 pdLog + 0xC0
[1] 0x09000000114BD444 sqlbLogReadAttemptFailure ... + 0x198
[2] 0x09000000114BE9CC sqlbLogReadAttemptFailure ... + 0x9C
[3] 0x0900000011AD892C sqlb_verify_page ... + 0x114
[4] 0x09000000126C1B50 sqlb_verify_page ... + 0x7C
[5] 0x0900000011CE9274 sqlbDMSMapAndRead ... + 0x47C
[6] 0x0900000014ABBDE8 sqlbDMSDirectRead ... + 0x88
[7] 0x0900000014ABB0B0 sqlbDirectRead ... + 0xC4
[8] 0x090000001232CA38 sqluDirectRead ... + 0xF8
[9] 0x0900000012662DAC @148@sqluTransformMerge ... + 0x98
The stack shows sqluTransformMergeFSCRRequest function which
causes this logical bad page error. Bad page error is logical
error when multiple edus are trying to write to the same page.
This is a rare timing issue and will not happen on every load on
a range partitioned table.
This APAR is hit only under the following conditions :
1. Load is done on range partitioned table
2. Load has disk parallelism greater than 1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* see above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5 or later *
**************************************************************** |
| Local Fix: |
One of the following can work around the problem :
1. Use DISK_PARALLELISM 1 clause in Load command.
2. This is rare timing issue so restarting the load should not
hit the bad page. |
| available fix packs: |
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
|
| Solution |
Upgrade to DB2 Version 9.7 Fix Pack 5 or later |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC78264
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.07.2011
04.01.2012
04.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
