|
Problem IC80373
|
Status: Closed |
DATABASE MAY ABEND WITH SQLD_BADPAGE ERROR FROM SQLDINCREMENTRESERVEDSPACE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During a reclustering inplace table reorg with the truncate
table option, incorrect handling of an empty page may cause
errors.
The problem occurs while moving rows within the table. If the
last page is empty, but there appears to be valid data on the
page, an attempt is made to move that data to a new location in
the table. This can cause various different problems.
If the page size is 32k, the database may abend with a message
similar to this seen in the db2diag.log:
2011-11-21-20.47.02.766793-300 I41112633A574 LEVEL:
Severe
PID : 15270102 TID : 46275 KTID :
100663387
PROC : db2sysc 0
INSTANCE: svtdbm2 NODE : 000 DB :
SAMPLEXX
APPHDL : 0-53725 APPID: *N0.DB2.111121233626
AUTHID : SVTDBM2
EDUID : 46275 EDUNAME: db2reorg (SAMPLEXX) 0
FUNCTION: DB2 UDB, data management, sqldIncrementReservedSpace,
probe:8795
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
Page"
DIA8500C A data file error has occurred, record id is
"".
and the following stack would be seen:
0x0900000027FD466C sqloDumpEDU
0x09000000283BB838
sqldDumpBadPage__FP8sqeAgentP8SQLD_TCBP13SQLD_PAGESLOTP11SQLB_FI
X_CBUliT6
0x090000002EF2DAA8
sqldIncrementReservedSpace__FP13SQLD_DFM_WORKPi
0x090000002EF43ED4
sqldOLRUpdateRow__FP13SQLD_DFM_WORKP9SQLP_LSN8PlT3
0x090000002EF46324
sqldConvertNormalToRP__FP13SQLD_DFM_WORKPlP9SQLP_LSN8
0x090000002EEFD258 sqldFillNormalRecord__FP13SQLD_DFM_WORKT1
0x090000002EF0ABA0
sqldOLRFill__FP8SQLD_CCBPiT2P18SQLD_OLR_INTERRUPT
0x090000002EF232C4
sqldOnlineTableReorg__FP8sqeAgentUsT2UcUliT2PcT6T8T6P9SQLP_LSN8T
12_s
0x090000002EEDF60C sqldOLRInvoke__FP8sqeAgentPc
If the page size is smaller than 32k, a non-existent row will
have been added to the table, resulting in possible incorrect
results. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of inplace table reorg *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 UDB version 9.7 fix pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.12.2011
04.06.2012
04.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
