|
Problem IT37671
|
Status: Closed |
TABLE SPACE ROLLFORWARD CAN FAIL UNDER ADVANCED LOG SPACE MANAGEMENT
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
If a database is configured with Advanced Log Space Management
(ALSM) a table space rollforward may fail with a data page
error. If a table space rollforward fails, one possible
db2diag.log entry can look like the following:
EDUID : 35469 EDUNAME: db2agent (FITDB) 0
FUNCTION: DB2 UDB, data management, sqldFetchDirect, probe:5715
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
Page"
DIA8500C A data file error has occurred, record id is
"".
But there could be other functions reporting a data page error
or a table space container error. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Databases enabled with Advanced Log Space Management. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.0. *
**************************************************************** |
| Local Fix: |
1. Set DB2_COLLECT_TS_REC_INFO=OFF.
2. Restore all table spaces involved in the failing rollforward
operation.
3. Re-issue the failing table space rollforward operation. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Databases enabled with Advanced Log Space Management. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.0. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.7.0. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.07.2021
09.08.2021
09.08.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
