|
Problem IC84857
|
Status: Closed |
PERFORMING MEMBER CRASH RECOVERY IN PURESCALE THAT REPLAYS CERTAIN LOAD OR REORG LOG RECORDS MIGHT CORRUPT THE INDEX |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Error Description:
The corruption could occur if the Member Crash Recovery needs to
replay page initialization log records against the index object
that were written by either:
- The LOAD command when run with the INDEXING MODE INCREMENTAL
option (specified either explicitly or implicitly) and with the
database configuration parameter LogIndexBuild turned on.
- The REORG INDEX or REORG INDEXES ALL commands when run with
the ALLOW NO ACCESS option and with the database configuration
parameter LogIndexBuild turned on.
Some of the pages might not get initialized properly and causing
corruption in the index.
If the index pages are corrupted in this way the following error
might be seen in the diag:
FUNCTION: DB2 UDB, buffer pool services, sqlbGetPageFromDisk,
probe:931
MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page
Header"
DIA8547C An error occurred in a database page header.
[1] 0x090000001314E4F4 sqlbGetPageFromDisk__FP11SQLB_FIX_CBi +
0x1114
[2] 0x090000000C1A0724 sqlbfix__FP11SQLB_FIX_CB + 0x3564
[3] 0x0900000012C7D8C0 sqlbFixPage__FP11SQLB_FIX_CBiUiT2 +
0x280
[4] 0x0900000012C7DA80
sqlbFixOrCreatePage__FP11SQLB_FIX_CBiUiT2PFP8sqeAgentP9SQLB_PAGE
Pv_vPv + 0x160
[5] 0x0900000012C8175C
sqliRedoGetNewPage__FP8sqeAgentP16SQLB_OBJECT_DESCP8GTPG_LOGP9SQ
LP_LSN8UlUi + 0x25C
[6] 0x0900000012C8E010
sqliRedo__FP8sqeAgentPcUsP9SQLP_LSN8UlT5 + 0x4B50
[7] 0x090000000BCDCE84
sqldmrdo__FP8sqeAgentUsP9SQLP_LSN8PcUlN35P8SQLP_TIDP15SQLD_RECOV
_INFO + 0x544
[8] 0x090000000D5B6A50
sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP10SQLP_FRA
PPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x12F0
[9] 0x090000000D5BCE5C
sqlpPRecProcLog__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb + 0x8BC
[10] 0x090000000F564C28
sqlpParallelRecovery__FP8sqeAgentP5sqlca + 0xC88
[11] 0x09000000138D4AC4
sqleSubCoordProcessRequest__FP8sqeAgent + 0x1E4
[12] 0x090000000A5335B4 RunEDU__8sqeAgentFv + 0x354 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* PURESCALE USERS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.1. *
**************************************************************** |
| Local Fix: |
Using db2dart to mark the index object invalid prior to retrying
Member Crash Recovery. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 version 10.1.0.1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2012
31.10.2012
31.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
