|
Problem IT39261
|
Status: Closed |
IMPROVE ERROR MESSAGE WHEN PUTTING CLUSTER IN TO MAINTENANCE MODE WITHOUT DB2CLUSTER -ALL OPTION.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When putting all the nodes in the pureScale cluster into
maintenance mode, "db2cluster -cm -enter -maintenance -all" and
"db2cluster -cfs -enter -maintenance -all" commands should be
used.
If each of the nodes are put into maintenance mode without the
-all option, db2 cluster command fails because there are not
enough hosts online in the cluster.
-------------------------------
There are not enough hosts in the RSCT peer domain to enter
db2cluster maintenance mode. Exit maintenance on another host in
order to enter maintenance on host1.
A diagnostic log has been saved to
'/tmp/ibm.db2.cluster.68tMea'.
-------------------------------
Rebooting that last host while all other hosts are in
maintenance will
cause the cluster to go into a problematic state, where the
domain
would not be able to become online. This fix will aim to
improve the error message so that the error message will not be
missed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 pureScale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product 11.5.7.0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2 pureScale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product 11.5.7.0 *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.11.2021
01.12.2021
01.12.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
