DB2 - Problem description
Problem IT09018 | Status: Closed |
HADR STANDBY LOG REPLAY OR ROLLFORWARD RECOVERY CAN FAIL DUE TO SQLB_BAD_PAGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
During HADR replay or roll forward recovery, an insert may fail due to a bad page being returned from disk. There are at least two possible symptoms for this problem. Symptom #1: You will see messages in the db2diag.log similar to the following. 2015-05-12-21.32.51.442700+480 I847140A6049 LEVEL: Warning PID : 3473428 TID : 19020 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-9 APPID: *LOCAL.DB2.150509115048 HOSTNAME: myHost EDUID : 19020 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbGetPageFromDisk, probe:932 MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page Header" DIA8547C An error occurred in a database page header. DATA #1 : String, 39 bytes Page from disk doesn't match obj or BPD DATA #2 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes pageHead: {tbspSeed:8;obj:5142;type:0} PPNum:793865 OPNum:793865 begoff: 48 datlen: 4048 pagebinx: 2146491 revnum: 1280 pagelsn: 0000000F3EA2F29E flag: 2a future32: 0 cbits1to31: 1769af10 cbits32to63: 3f06533b DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 256 bytes Pagekey: {pool:8;obj:5142;type:0} PPNum:801673 objectPageNum: 793865 ... CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000000459EE1C sqlbGetPageFromDisk__FP11SQLB_FIX_CBi + 0x950 [1] 0x09000000064C8654 sqlbfix__FP11SQLB_FIX_CB + 0x1724 [2] 0x09000000087BC578 @113@sqldRedoUpsert__FP13SQLD_DFM_WORKP15SQLD_INSINFO_LRP9SQLP_L SN8Ul + 0x2780 [3] 0x09000000087A08A8 sqldRedo__FP8sqeAgentP8SQLD_LRHP9SQLP_LSN8UlN24 + 0x87C [4] 0x0900000008AE759C sqldmrdo__FP8sqeAgentUsP9SQLP_LSN8PcUlN35P8SQLP_TIDP15SQLD_RECOV _INFO + 0x5E8 [5] 0x0900000008F3CA4C sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP10SQLP_FRA PPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x928 [6] 0x0900000005282300 sqlpPRecProcLog__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb + 0xBCC [7] 0x090000000527E4C4 sqlpParallelRecovery__FP8sqeAgentP5sqlca + 0x1918 [8] 0x0900000007331D74 sqleSubCoordProcessRequest__FP8sqeAgent + 0x198 [9] 0x0900000006858724 RunEDU__8sqeAgentFv + 0x6FC [10] 0x0900000006855ACC EDUDriver__9sqzEDUObjFv + 0x13C [11] 0x0900000006855954 sqlzRunEDU__FPcUi + 0x10 [12] 0x0900000006868CD8 sqloEDUEntry + 0x264 [13] 0x0900000000839E10 _pthread_body + 0xF0 [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2015-05-12-21.32.51.479896+480 I853190A530 LEVEL: Severe PID : 3473428 TID : 19020 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-9 APPID: *LOCAL.DB2.150509115048 HOSTNAME: myHost EDUID : 19020 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, data management, sqldRedo, probe:8503 RETCODE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page Header" DIA8547C An error occurred in a database page header. 2015-05-12-21.32.51.480241+480 I853721A648 LEVEL: Severe PID : 3473428 TID : 19020 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-9 APPID: *LOCAL.DB2.150509115048 HOSTNAME: myHost EDUID : 19020 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, data management, sqldmrdo, probe:1250 MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page Header" DIA8547C An error occurred in a database page header. DATA #1 : String, 25 bytes Error during REDO of LSN: DATA #2 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes 0000000F7EF0221B 2015-05-12-21.32.51.490418+480 E854370A594 LEVEL: Error PID : 3473428 TID : 19020 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-9 APPID: *LOCAL.DB2.150509115048 HOSTNAME: myHost EDUID : 19020 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbSetPoolState, probe:3604 MESSAGE : ADM12512W Log replay on the HADR standby has stopped on table space "HIS_DATA_TBS" (ID "8") because it has been put into "ROLLFORWARD PENDING" state. Symptom #2: You will see messages in the db2diag.log similar to the following. 2016-01-19-14.18.29.147786-360 I113105A1691 LEVEL: Severe PID : 8847738 TID : 26730 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-41234 APPID: *LOCAL.DB2.160115033237 HOSTNAME: myHost EDUID : 26730 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:2245 MESSAGE : Free Space does not match during redo! DATA #1 : String, 11 bytes insinfo_lr: DATA #2 : Hexdump, 26 bytes 0x0A00041DCEC876D8 : 01A2 0851 0004 0000 005C 0F5E 001D 79EF ...Q.....\.?..y. 0x0A00041DCEC876E8 : 0000 0F60 0000 005C 0100 ...`...\.. DATA #3 : String, 11 bytes Space used: DATA #4 : signed integer, 4 bytes 92 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000008319D80 sqldRedo__FP8sqeAgentP8SQLD_LRHP9SQLP_LSN8UlN24 + 0x5BC4 [1] 0x090000000830AB08 sqldRedo__FP8sqeAgentP8SQLD_LRHP9SQLP_LSN8UlN24 + 0x120 [2] 0x090000000B96DDC0 sqldmrdo__FP8sqeAgentUsP9SQLP_LSN8PcUlN35P8SQLP_TIDP15SQLD_RECOV _INFO + 0x8C4 [3] 0x0900000009382D7C sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP10SQLP_FRA PPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO _INPUT + 0xAAC [4] 0x090000000B452D14 RunEDU__8sqeAgentFv + 0x10ECC [5] 0x090000000B451960 RunEDU__8sqeAgentFv + 0xFB18 [6] 0x090000000B44DA90 RunEDU__8sqeAgentFv + 0xBC48 [7] 0x090000000B3FFF10 RunEDU__8sqeAgentFv + 0x124 [8] 0x090000000C75BB28 EDUDriver__9sqzEDUObjFv + 0x134 [9] 0x090000000B3F4B30 sqloEDUEntry + 0x398 [10] 0x09000000004F5E10 _pthread_body + 0xF0 [11] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2016-01-19-14.18.29.151245-360 I114797A548 LEVEL: Severe PID : 8847738 TID : 26730 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-41234 APPID: *LOCAL.DB2.160115033237 HOSTNAME: myHost EDUID : 26730 EDUNAME: db2redow (MYDB) 0 FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:2251 RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data Page" DIA8500C A data file error has occurred, record id is "". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.6. * **************************************************************** | |
Local Fix: | |
If hit on the standby machine in an HADR pair, then reinitialize the standby database from the primary database. If hit during crash recovery or rollforward recovery, contact IBM DB2 Support or restore a backup and rollforward to an earlier point in time. | |
Solution | |
The problem is first fixed in DB2 version 10.5.0.6. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.05.2015 14.08.2015 21.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.6 |