DB2 - Problem description
| Problem IC81700 | Status: Closed |
ONLINE EXTENT MOVE OF LOB EXTENTS USING INDIRECT EMP PAGES WILL RESULT IN PAGES WITH A BAD PAGE HEADER | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
Alter tablespace lower high water mark will initiate an online
extent movement. This is part of a 9.7 feature called
reclaimable storage.
If there are enough LOB pages in the table to require the use of
indirect extent maps entries, then online extent movement will
fail to properly update the pool page numbers for the moved
extents.
The number of page required to use indirect extent map entries
depends on the page size and extent size. The following chart
describes how many LOB pages are required to use indirect extent
map entries
Page size 4096
Extent size Number of pages
2 2002
4 12004
8 56008
16 240016
32 992032
Page size 8192
Extent size Number of pages
2 4054
4 24316
8 113464
16 486256
32 2009824
Page size 16384
Extent size Number of pages
2 8150
4 48892
8 228152
16 977776
32 4041440
Page size 32768
Extent size Number of pages
2 16342
4 98044
8 457528
16 1960816
32 8104672
A typical error reported in the db2diag.log file would be
2012-02-28-13.12.26.069274-300 I184962A3753 LEVEL: Severe
PID : 9044090 TID : 5758 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-381 APPID:
*LOCAL.db2inst1.120228181055
AUTHID : DB2INST1
EDUID : 5758 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,
probe:5
MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page
Header"
DIA8547C An error occurred in a database page header.
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
13218
DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 88 bytes
Obj: {pool:3;obj:6;type:67} Parent={3;6}
lifeLSN: 000000000F46941C
tid: 0 0 0
extentAnchor: 15384
initEmpPages: 0
poolPage0: 0
poolflags: 3122
objectState: 27
lastSMP: 0
pageSize: 4096
extentSize: 2
bufferPoolID: 1
partialHash: 1124466691
bufferPool: 0x0700000041f513c0
pdef: 0x0700000041fd0aa0
DATA #5 : Bitmask, 4 bytes
0x00000002
DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes
pageHead: {tbspSeed:3;obj:6;type:67} PPNum:19772 OPNum:2
begoff: 48
datlen: 4048
pagebinx: 854
revnum: 1280
pagelsn: 0000000011122380 flag: a
future32: 0
cbits1to31: 0
cbits32to63: 0
The type will be 67 in both DATA #4 and DATA #6 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 * **************************************************************** | |
| Local Fix: | |
Avoid running alter tablespace lower high water mark on tablespaces where the number of LOB pages for an individual object exceed the numbers in the above matrix | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 9.7 Fix Pack 6 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.02.2012 06.06.2012 06.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|