DB2 - Problem description
Problem IT28912 | Status: Closed |
AFTER HADR STANDBY IS RESTARTED, DB2PD -HADR NO LONGER REPORTS TABLESPACE IN RESTORE PENDING STATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When HADR standby database first encounters a condition that caused a tablespace to be put into restore pending state (eg. due to LOAD COPY file is not available on standby server), user is made aware of this condition from db2pd -hadr where the HADR_FLAGS field would have STANDBY_TABLESPACE_ERROR and the STANDBY_ERROR_TIME field would report the time the tablespace state is changed. However, after the standby database is restarted (via either DEACTIVATE / ACTIVATE DATABASE or STOP HADR / START HADR commands), the condition is no longer being reported by db2pd -hadr while the problematic tablespace is still in restore pending state. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.04.2019 16.03.2020 16.03.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |