DB2 - Problem description
Problem IT36225 | Status: Closed |
HADR START SCRIPT MAY INCORRECTLY RETURN SUCCESSFUL WHEN INSTANCE IS DOWN | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In an HADR environment, the hadrVxxx_start.ksh script may incorrectly detect a successful Db2 start despite the Db2 instance being down. This may prevent any further automated recovery of the database and start of the db2 instance for up to 50 minutes. If encountered the following would be seen in the var/log/messages or syslogs on a host where the instance is down: Jan 20 22:22:42 hadrVxxx_start.ksh[18641]: Returning 0 : SAMPLE_DB which may be followed by repeated monitor command failures such as below: Jan 20 22:23:09 GblResRM[26062]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: 0:::Details File: :::Location: RSCT,Application.C,1.23.4.5678,6131:::GBLRESRM_MONITOR_TIMEOUT#0 12IBM.Application monitor command timed out.#012Resource name#012db2_db2inst1_db2inst1_-rs A local fix is available via a patched start script. Contact Db2 for this script. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Db2 HADR prior to 11.1.4.6 or 11.5.5.0 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Contact Db2 support for updated HADR start script or upgrade * * to latest fix pack. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Db2 HADR prior to 11.1.4.6 or 11.5.5.0 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Contact Db2 support for updated HADR start script or upgrade * * to latest fix pack. * **************************************************************** | |
Comment | |
Problem was first fixed in Db2 Version 11.1 Mod 4 Fix Pack 6 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.03.2021 15.03.2021 15.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |