|
Problem IT05568
|
Status: Closed |
RUNNING 'DB2STOP FORCE' ON PASSIVE NODE OF MSCS CLUSTER CAN CAUSE THE INSTANCE TO HANG DURING SHUTDOWN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When running with a ESE instance in a DB2 MSCS cluster
configuration running 'db2stop' or 'db2stop force' on either
node should trigger a cluster resource failure and the DB2
instance should get restarted or failover depending on the
configured action.
Running 'db2stop force' on the passive node can cause the
instance to hang during shutdown and not trigger a resource
failure. The Cluster Administration user interface shows that
the DB2 resource is still 'Running'. Running 'db2stop force'
shows the following message
C:\windows>db2stop force
SQL6033W Stop command processing was attempted on "1" node(s).
"0"
node(s) were successfully stopped. "0" node(s) were already
stopped. "0" node(s)
could not be stopped.
Ending and restarting the cluster resource using the Cluster
Administration interface allows the DB2 instance to restart
successfully. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 MSCS users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 5 *
**************************************************************** |
| Local Fix: |
End the DB2 instance using the Cluster Administration interface. |
| Solution |
First fixed in DB2 10.1 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.11.2014
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
