|
Problem IT30789
|
Status: Closed |
ROLLFORWARD MAY FAIL WITH SQL1271W AND SQLB_TBSPACE_TOO_SMALL WHEN REPLAYING AN ALTER TABLESPACE OPERATION
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Rollforwarding through a FREE_PENDDEL log record may incorrectly
calculate a table space?s high water mark (HWM) and a subsequent
ALTER_POOL log record may fail with the following error in
db2diag.log:
2019-06-07-16.10.49.183375-240 I452476E791 LEVEL:
Error
PID : 28077 TID : 140059818845952 KTID :
29441
PROC : db2sysc
INSTANCE: XXXXXXXX NODE : 000 DB :
XXXXXXXX
APPHDL : 0-15 APPID: XXXXXXXX
AUTHID : XXXXXXXX HOSTNAME: XXXXXXXX
EDUID : 413 EDUNAME: db2redom (XXXXXXXX)
FUNCTION: DB2 UDB, buffer pool services,
sqlbValidateContOpsMain, probe:150
MESSAGE : ZRC=0x8002013A=-2147352262=SQLB_TBSPACE_TOO_SMALL
"Cannot reduce tablespace size as requested"
DATA #1 :
useablePages is less than the High Water Mark
or usedPages is greater than the High Water Mark
useablePages = 32000
HighWaterMark = 6
usedPages = 16006
Table space ID = 3
The HWM is calculated using the wrong SMP page and the resulting
HWM may be less than useablePages and usedPages. The rollforward
will fail with:
SQL1271W Database "" is recovered but one or more table
spaces are
offline on members or nodes "".
The table space will be put in the ROLLFORWARD_PENDING state.
LOCAL FIX:
None. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.5 or later *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT29380
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.10.2019
31.10.2019
31.10.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
