|
Problem IT40544
|
Status: Closed |
DATABASE NOT SHUTDOWN WHEN LOAD REPLAY FAILS ON HADR STANDBY WITH DB2_FAIL_RECOVERY_ON_TABLESPACE_ERROR ENABLED
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
With DB2_FAIL_RECOVERY_ON_TABLESPACE_ERROR is enabled, HADR
standby database encountering an error during replay of LOAD
operation cannot shutdown.
The issue only exists in 11.5.7.
The following db2diag.log messages is an example of the events
leading to the problem.
As shown above, the standby database was actually shutdown when
encountering the load replay error for the first time. Db2 has
a self-healing logic to automatically activate the HADR standby
database again, in case the previous error is transient. On the
subsequent activation, the same load replay error was
encountered, and this is where the handling is incorrect and the
database is not able ot shutdown and requires manual
intervention.
The self-healing feature can be disable by setting the internal
register variable DB2_STANDBY_REPLAY_MAX_AUTO_RESTART_ATTEMPTS
to 0. This can be used as a workaround to avoid the problem. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db1 11.5.8.0 or higher *
**************************************************************** |
| Local Fix: |
Issue can be avoided by using db2set
DB2_STANDBY_REPLAY_MAX_AUTO_RESTART_ATTEMPTS=0 |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db1 11.5.8.0 or higher *
**************************************************************** |
| Comment |
Upgrade to Db1 11.5.8.0 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.04.2022
28.04.2022
28.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
