Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
Users Affected All users on V9.1 and V9.5 on Linux, Unix and Windows platforms that use load to add data into a range partitioned table Problem Description When using load to add data to a range partitioned table, a bad page can be reported by one of the db2lbm processes. Entries in the db2diag.log will include 2008-05-07-17.30.43.287920-240 I25882E2464 LEVEL: Severe PID : 21516 TID : 183044631104PROC : db2lbm1 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.db2inst1.080507213026 AUTHID : DB2INST1 FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, probe:3 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 27536 DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 72 bytes Obj: {pool:3;obj:9;type:0} Parent={3;9} lifeLSN: 00000DAC3618 tid: 0 0 0 extentAnchor: 416 initEmpPages: 0 poolPage0: 448 poolflags: 122 objectState: 27 lastSMP: 0 pageSize: 4096 extentSize: 32 bufferPoolID: 1 partialHash: 589827 bufferPool: 0x0000000220598540 DATA #5 : Bitmask, 4 bytes 0x00000200 DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes pageHead: {pool:0;obj:0;type:0} PPNum:0 OPNum:0 begoff: 0 datlen: 0 pagebinx: 0 revnum: 0 pagelsn: 000000000000 flag: 0 signature: 0 cbits1to31: 0 cbits32to63: 0 DATA #3 and DATA #4 describe the page that DB2 is expecting to find on disk. DATA #6 is the page that was retrieved from disk. The contents of DATA #6 will vary, and be whatever was on disk before beginning the load. The stack trace of the db2lbm process will include sqlbLogReadAttemptFailure sqlb_verify_page sqluDirectRead sqluTransformMergeFSCRRequest sqluSetCBitsAndWriteBuf sqlulBMCont sqlulbuf Workaround Include the 'DISK_PARALLELISM 1' option in the load command
Local fix
Include the 'DISK_PARALLELISM 1' option in the load command
Problem summary
Users Affected All users on V9.1 and V9.5 on Linux, Unix and Windows platforms that use load to add data into a range partitioned table Problem Description When using load to add data to a range partitioned table, a bad page can be reported by one of the db2lbm processes. Entries in the db2diag.log will include 2008-05-07-17.30.43.287920-240 I25882E2464 LEVEL: Severe PID : 21516 TID : 183044631104PROC : db2lbm1 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.db2inst1.080507213026 AUTHID : DB2INST1 FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, probe:3 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 27536 DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 72 bytes Obj: {pool:3;obj:9;type:0} Parent={3;9} lifeLSN: 00000DAC3618 tid: 0 0 0 extentAnchor: 416 initEmpPages: 0 poolPage0: 448 poolflags: 122 objectState: 27 lastSMP: 0 pageSize: 4096 extentSize: 32 bufferPoolID: 1 partialHash: 589827 bufferPool: 0x0000000220598540 DATA #5 : Bitmask, 4 bytes 0x00000200 DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes pageHead: {pool:0;obj:0;type:0} PPNum:0 OPNum:0 begoff: 0 datlen: 0 pagebinx: 0 revnum: 0 pagelsn: 000000000000 flag: 0 signature: 0 cbits1to31: 0 cbits32to63: 0 DATA #3 and DATA #4 describe the page that DB2 is expecting to find on disk. DATA #6 is the page that was retrieved from disk. The contents of DATA #6 will vary, and be whatever was on disk before beginning the load. The stack trace of the db2lbm process will include sqlbLogReadAttemptFailure sqlb_verify_page sqluDirectRead sqluTransformMergeFSCRRequest sqluSetCBitsAndWriteBuf sqlulBMCont sqlulbuf
Problem conclusion
Problem was first fixed in Version 9.1 Fix Pack 6
Temporary fix
Comments
APAR Information
APAR number
IZ22385
Reported component name
DB2 DPF
Reported component ID
5724N7400
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-15
Closed date
2009-03-31
Last modified date
2009-03-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 DPF
Fixed component ID
5724N7400
Applicable component levels
R910 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
31 March 2009