DB2 - Problem description
Problem IC73673 | Status: Closed |
FAILED_OFFLINE STATE PERSISTS AFTER STANDBY DATABASE RETURNS TO PEER STATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Currently in integrated HA with HADR setup, if the Primary machine is rebooted, the Standby will takeover to become new Primary as expected. When the old Primary machines comes back alive, it is expected to become the new Standby (reintegration) such that the hadr pair resume Peer state with no manual intervention. This does happen at the DB2 level (verified by db2pd -hadr). However, at the SA MP level, lssam will show the old Primary is still "FAILED OFFLINE" despite HADR db pair is already in Peer. This TSA resource state can be set only via running SA MP command "resetrsrc" manually or recreating the cluster. If the "FAILED OFFLINE" state is not reset and a second failure occur, the next failover attempt will fail. This APAR fix will eliminate the need to manually run the "resetrsrc" command after reintegration occurs. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * HA/HADR integrated solution users * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Apply V97FP4 * **************************************************************** | |
Local Fix: | |
Run reintegration, manually run the following SA MP command: resetrsrc -s "Name = '<hadr_resource_name>' AND NodeNameList = {'<current_standby_node>'}" IBM.Application | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
After applying the fix, the SA MP resource state will change from Failed Offline back to Offline automatically after successful reintegration of old Primary database. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.01.2011 28.04.2011 28.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |