|
Problem IT29381
|
Status: Closed |
A FAILURE WHILE REPLAYING A TABLE SPACE LOG RECORD MAY CAUSE SUBSEQUENT ROLLFORWARDS TO CORRUPT THE TABLE SPACE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
If an error is encountered when rollforwarding through a table
space specific log record (i.e. ALTER_POOL, FREE_PENDDEL,
GET_ONE_EXT, ect.) the table space rollforward is supposed to
stop and put the table space in the ROLLFORWARD_PENDING state.
The table space state may not be written to disk and subsequent
rollforwards will continue assuming the table space is in a
NORMAL state. This causes the rollforward to start at the wrong
log sequence number (LSN) and may corrupt the table space.
This error can go undetected and can lead to various other
errors such as:
FUNCTION: DB2 UDB, buffer pool services, sqlbRedoGetOneExt,
probe:460
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error detected"
DIA8501C A buffer pool logic error has occurred.
db2dart or INSPECT will be able to identify that the table space
is corrupted.
LOCAL FIX:
None. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.06.2019
16.01.2020
16.01.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
