DB2 FOR LUW / DB2FORLUW / B10 - DB2

During HADR replay or roll forward recovery, an insert may fail
due to a bad page.  You will see
messages in the db2diag.log similar to the following.

2017-12-06-20.50.32.822597+480 I4082122A6053        LEVEL:
Warning

PID     : 4260556              TID : 20054          PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   : KSDBS

APPHDL  : 0-48199              APPID: *LOCAL.DB2.171202122723
HOSTNAME: p780_htjy3

EDUID   : 20054                EDUNAME: db2redow (KSDBS) 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:1757550
OPNum:1757550
  begoff:                      48
  datlen:                    4048
  pagebinx:               2305259
  revnum:                    1280
  pagelsn:     000000873C9FF178
  flag:                        2a
  future32:                    0
  cbits1to31:            df6ed884
  cbits32to63:           48d56f47
DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 256 bytes
    Pagekey: {pool:8;obj:5142;type:0} PPNum:1818030
  objectPageNum:                   1757550
  bucketGroupHashIndex:             153539
  hashnext:             0x0a00030028e1b020




2017-12-06-20.50.44.344296+480 I4091582A432         LEVEL: Info
  extentSize:                    64
  bufferPoolID:                   1
  partialHash:            336986120
  objDescAttributes:                  0
  bufferPool:    0x0a00020049e09440
  pdef:          0x0a0002004bc1aa60
  glob:          0x0000000112bda340
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved
to the nearest symbol)
  [0] 0x0900000007F9A2B4 sqlbGetPageFromDisk__FP11SQLB_FIX_CBi +
0x228
  [1] 0x09000000085A7568 sqlbfix__FP11SQLB_FIX_CB + 0x1714
  [2] 0x090000000BD11EF0
@114@sqldRedoUpsert__FP13SQLD_DFM_WORKP15SQLD_INSINFO_L
RP9SQLP_LSN8Ul + 0x276C
  [3] 0x090000000BCF4430
sqldRedo__FP8sqeAgentP8SQLD_LRHP9SQLP_LSN8UlN24 + 0x830
  [4] 0x090000000A443898
sqldmrdo__FP8sqeAgentUsP9SQLP_LSN8PcUlN35P8SQLP_TIDP15S
QLD_RECOV_INFO + 0x5E8
  [5] 0x09000000077B7204
sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP1
0SQLP_FRAPPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT +
0x934
  [6] 0x09000000078AC2D4
sqlpPRecProcLog__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb
+ 0xBCC
  [7] 0x09000000078A7A3C
sqlpParallelRecovery__FP8sqeAgentP5sqlca + 0x2070
  [8] 0x0900000006FC6854 sqleSubCoordProcessRequest__FP8sqeAgent
+ 0x1A0
  [9] 0x09000000089096B8 RunEDU__8sqeAgentFv + 0x704
  [10] 0x0900000008905858 EDUDriver__9sqzEDUObjFv + 0x13C
  [11] 0x09000000089056E0 sqlzRunEDU__FPcUi + 0x10
  [12] 0x09000000088F46A0 sqloEDUEntry + 0x268
  [13] 0x0900000000839E10 _pthread_body + 0xF0
  [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF

In the log record, there will be a INSREC_DP log record before a
MULTI_PAGE_CREATE_DP that creates the page where the insert is
suppose to go

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************

not known / see Local fix

forerunner  : IT24663 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.04.2018
27.11.2018
27.11.2018