|
Problem IT03382
|
Status: Closed |
'DB2IDROP' COMMAND REMOVES NON-DB2 MANAGED RSCT CLUSTER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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
=========================================== |
| Solution |
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
=========================================== |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.07.2014
10.11.2014
10.11.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.10
|
 |
