|
Problem IC67624
|
Status: Closed |
IN RARE TIMING SCENARIOS, LOAD UTILITY INTO A RANGE PARTITIONED TABLE MAY TRAP WITH BAD PAGE ERROR IN SQLB_VERIFY_PAGE |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
When using Load utility to add data into a range partitioned
table, a BAD PAGE error can be reported by one of the db2lbm
processes.
db2diag.log will include an entry similar to this::
2010-02-05-02.24.11.305740+540 I60623A3957 LEVEL: Severe
PID : 1151192 TID : 511867 PROC : db2sysc
0
INSTANCE: XXXXXXXX NODE : 000 DB : XXXXX
APPHDL : 0-18593 APPID:
XXX.XXX.XXX.XXX.41515.100204113503
AUTHID : XXXXX
EDUID : 511867 EDUNAME: db2lbm0 0
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.
Stack trace generated by error may contain entries like this:
sqlb_verify_page
[...]
sqluDirectRead
sqluTransformSendToCopyRequest
sqluSetCBitsAndWriteBuf
sqlulBMCont
sqlulbuf
sqloEDUEntry
The problem may be more suseptible when the COPY YES option is
used.
Per usual Load recovery usage, execute a Load Terminate to bring
the table back to consistent state, then you can try the Load
again. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* When using Load utility to add data into a range partitioned *
* table, a BAD PAGE error can be reported by one of the db2lbm *
* processes. *
* *
* db2diag.log will include an entry similar to this:: *
* *
* 2010-02-05-02.24.11.305740+540 I60623A3957 LEVEL: *
* Severe *
* PID : 1151192 TID : 511867 PROC : *
* db2sysc 0 *
* INSTANCE: XXXXXXXX NODE : 000 DB : XXXXX *
* APPHDL : 0-18593 APPID: *
* XXX.XXX.XXX.XXX.41515.100204113503 *
* AUTHID : XXXXX *
* EDUID : 511867 EDUNAME: db2lbm0 0 *
* 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. *
* *
* Stack trace generated by error may contain entries like *
* this: *
* *
* sqlb_verify_page *
* [...] *
* sqluDirectRead *
* sqluTransformSendToCopyRequest *
* sqluSetCBitsAndWriteBuf *
* sqlulBMCont *
* sqlulbuf *
* sqloEDUEntry *
* *
* The problem may be more suseptible *
* when the COPY YES option is used. *
* *
* Per usual Load recovery usage, execute a Load Terminate to *
* bring the table back to consistent state, then you can try *
* the Load again. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.1 fix pack 10. *
**************************************************************** |
| Local Fix: |
Use DISK_PARALLELISM 1 to avoid the problem (this may have some
performance impact).
Avoiding COPY YES option may also reduce the probability of
hitting the problem. |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.1 Fix Pack 10. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.04.2010
13.06.2011
13.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
