home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02557 Status: Geschlossen

SQLB_BADHDR "BAD PAGE HEADER" ENCOUNTERED DURING CLASSIC REORG OF
AN INSERT TIME CLUSTERING TABLE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
If a REORG TABLE ... RECLAIM EXTENTS is performed on an insert 
time clustering (ITC) table that resides in a non-storage 
reclaimable tablespace, a subsequent classic REORG TABLE 
operation on that table may abend with a bad page error.  You 
would see a message similar to the following written to the 
db2diag.log: 
 
2014-06-12-11.32.27.56-240             LEVEL: Severe 
PID     : 1414                 TID : 4694  PROC : db2sysc 
INSTANCE: xxxx                 NODE : 000            DB   : SB 
APPHDL  : 0-43                 APPID: *LOCAL.xxxx.140612152854 
AUTHID  : xxxx                 HOSTNAME: hotel64 
EDUID   : 18                   EDUNAME: db2agent (SB) 
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, 
probe:12 
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 
38 
DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 104 bytes 
    Obj: {pool:3;obj:4;type:0} Parent={3;4} 
    lifeLSN:       000000000003E1BD 
    tid:           0 0  0 
    extentAnchor:                   6 
    initEmpPages:                   0 
    poolPage0:                      8 
    poolflags:   0x              4122 
    objectState: 0x             80027 
    lastSMP:                        0 
  pageSize:                    4096 
  extentSize:                     2 
  bufferPoolID:                   1 
  partialHash:               262147 
  objDescAttributes:                  0 
  objDescEHLState: 0x00002aaafe8af228 
  bufferPool:    0x00002aaaf623f720 
  pdef:          0x00002aaaf89d7260 
DATA #5 : Bitmask, 4 bytes 
0x00000002 
DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes 
pageHead: {tbspSeed:3;obj:4;type:64} bphPPNum:38 bphOPNum:0 
  begoff:                      48 
  datlen:                    4048 
  revnum:                    1280 
  pagelsn:     000000000003E1CD 
  flag:                        2a 
  future32:                    0 
  cbits1to31:            2f572168 
  cbits32to63:            4e8fafe 
DATA #7 : Bufferpool globals, PD_TYPE_SQLB_GLOBALS, 1248 bytes 
  dbcb:                  0x0000000202180080 
  bpcb:                  0x00002aaaf61ca320 
  ptbl:                  0x00002aaaf61ca6c0 
  eduType:               SQLB_EDU_AGENT 
  eduCB:                 0x000000020212df60 
  qryData:               0x0000000000000000 
  qryDataSz:                              0 
  qryDataPos:                             0 
  contQryData:           0x0000000000000000 
  contQryDataSz:                          0 
  contQryDataPos:                         0 
  bglobals_flags:                       200 
  eduId:                 18 
  curPfQ:                                 5 
  curRemHateListCounter:                302 
  debugInfo:             0x0000000000000000 
  pCurRecLsn:            0x0000000000000000 
  clnrCB:                0x0000000000000000 
  prefetchPriority:                       1 
  agentPriorityWeight:      00 
  staticStr: 
  numPFRequestsHeld:                      0 
  memAccessCount: 
    m_bIsInitialized:                 false 
    m_iDisabled:                          0 
    m_iAccessCount:                       0 
 
and the failing agent will have the following stack: 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] sqlbLogReadAttemptFailure 
  [1] sqlb_verify_page 
  [2] sqlbReadPage 
  [3] sqlbGetPageFromDisk 
  [4] sqlbfix 
  [5] sqldFetchFromBlock 
  [6] sqldReorgBID 
  [7] processLeaf 
  [8] sqliScanLeafLvl 
  [9] sqldReorgIndexScan 
  [10] sqldReorgAllRecords 
  [11] sqldReorgDriver 
  [12] sqldTableReorgObject 
  [13] sqldTableReorg 
  [14] sqlrreorg_table 
  [15] sqlrreorg_sendinfo 
  [16] sqlrr_reorg
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of insert time clustering tables                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local-Fix:
The problem is with the block index which must be recreated by 
using db2dart to mark the indexes on the table for rebuild.  The 
next table access will rebuild and correct the index.
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in DB2 UDB Version 10.5 fix pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList