DB2 - Problembeschreibung
Problem IC77263 | Status: Geschlossen |
DB2 HA SCRIPT HADRV97_START.KSH CAN RETURN WITH RC 0 ON REDHAT LINUX AND AUTOMATIC FAILOVER WILL NOT BE PERFORMED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
On Redhat Enterprise Linux 5.5 there is an issue with the "su" command that is used in the hadrV97_start.ksh scripts to determine the server status. If the command gets killed by db2V97_start.ksh script - that can execute in parallel - then the return code of the su command remains 0 (zero). For TSA this indicates a false "successfull" startup and a potential failover will not be performed. In Linux system log (/var/log/messages) you will see the following messages: Oct 15 16:14:08 lx252 db2V97_start.ksh[2176]: *************** Attempted to start partition db2inst1,0 and failed Oct 15 16:14:08 lx252 db2V97_start.ksh[2177]: Killing db2 processes : db2inst1, 0 Oct 15 16:14:08 lx252 /usr/sbin/rsct/sapolicies/db2/hadrV97_start.ksh[2185]: ...returns 0 Oct 15 16:14:08 lx252 /usr/sbin/rsct/sapolicies/db2/hadrV97_start.ksh[2186]: Returning 0 : db2inst1 db21inst1 PDB2UID Note: This has been addressed already partially in APAR IC72271, db2gcf does not get killed anymore by the db2V97_start.ksh script. Unfortunately, there are two places in the script, where kill -9 is called, but only one call was fixed. This APAR will address the second call as well. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL Users on REDHAT Linux. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
Modify the db2V97_start.ksh script to exclude db2gcf in both "kill -9" calls. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC77264 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 30.06.2011 08.12.2011 08.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |