DB2 - Problembeschreibung
| Problem IT03382 | Status: Geschlossen |
'DB2IDROP' COMMAND REMOVES NON-DB2 MANAGED RSCT CLUSTER | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problembeschreibung: | |
When 'db2idrop' command is performed, it invokes 'db2haicu -delete' command as long as the 'db2haicu' utility is found. If there is non-DB2 managed RSCT cluster existing in the system, it will be removed by the 'db2haicu -delete' command. This might be unexpected result to some High Availability utility such as HACMP which also manages clusters. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users of version 9.7 on Linux, Unix and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to DB2 LUW Version 9.7 Fix Pack 10 or higher levels. * **************************************************************** | |
| Local-Fix: | |
Backup up the original 'db2iutil' script, then edit it and
comment out the lines that call 'db2haicu -delete' command.
Here is an example of how 'db2haicu -delete' command is invoked
in 'db2iutil' script:
===========================================
drop_instance ()
{
# Check that the specified user is a valid instance name and
# has an sqllib/bin directory in its home directory.
if [ ${DB2INSTVER?} != ${DB2VER_UNKNOWN?} ]; then
if [ -d ${INSTHOME?}/sqllib/bin ]; then
# Clean up HA resources
if [ -f ${INSTHOME?}/sqllib/bin/db2haicu ]; then
${DB2DIR?}/instance/db2iexec -n ${INSTNAME?}
"${INSTHOME?}/sqllib/bin/db2haicu -delete" 1>/dev/null
2>/dev/null
fi
=========================================== | |
| Lösung | |
First fixed in DB2 LUW Version 9.7 Fix Pack 10. | |
| Workaround | |
Backup up the original 'db2iutil' script, then edit it and
comment out the lines that call 'db2haicu -delete' command.
Here is an example of how 'db2haicu -delete' command is invoked
in 'db2iutil' script:
===========================================
drop_instance ()
{
# Check that the specified user is a valid instance name and
# has an sqllib/bin directory in its home directory.
if [ ${DB2INSTVER?} != ${DB2VER_UNKNOWN?} ]; then
if [ -d ${INSTHOME?}/sqllib/bin ]; then
# Clean up HA resources
if [ -f ${INSTHOME?}/sqllib/bin/db2haicu ]; then
${DB2DIR?}/instance/db2iexec -n ${INSTNAME?}
"${INSTHOME?}/sqllib/bin/db2haicu -delete" 1>/dev/null
2>/dev/null
fi
=========================================== | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.07.2014 10.11.2014 10.11.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP10 | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.10 |
|