|
Problem IT41420
|
Status: Closed |
TABLESPACE ROLLFORWARD IS VERY SLOW DUE TO EXCESSIVE NUMBER OF SQLBAFLSH() CALLS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
After a tablespace level restore, the rollforward operation can
be very slow due to excessively high number of sqlbaflsh()
calls made during the log replay for the tablespace rollforward
operation.
This can be confirmed from a short trace (eg. taken as part of
FODC -hang). As an example, for a 3 second trace, the output
from grep -c "sqlbaflsh entry" is over 3000.
This problem does not occur if the SOFTMAX database
configuration parameter is set to a non-zero value. So it can
be used as a workaround. Note that recycling the database is
required for the change to SOFTMAX to take effect. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users issuing tablespace rollforward with softmax set to *
* default or explicitly set to 0 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to product version 11.5.8 *
**************************************************************** |
| Local Fix: |
Temporary circumvention, set database configuration parameter to
non-zero value, eg. 100.
Note that recycling the database is
required for the change to SOFTMAX to take effect. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users issuing tablespace rollforward with softmax set to *
* default or explicitly set to 0 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to product version 11.5.8 *
**************************************************************** |
| Comment |
Fixed in 11.5.8 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.07.2022
03.08.2022
03.08.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
