|
Problem IT27164
|
Status: Closed |
DB2CLUSTER -CM -VERIFY -MAINTENANCE FAILS WHEN THE ENTIRE CLUSTER IS PUT INTO MAINTENANCE WITH DB2CLUSTER -CM -ENTER -MAINTENANC
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The db2cluster -cm -verify -maintenance checks for both
maintenance file and the localhost's peer domain to be down to
detect thatlocal host is in maintenance. This won't work for
"db2cluster-cm -enter -maintenance -all" since it won't write
the maintenance file. This causes "db2cluster -cm
-verify-maintenance" to report that the host is not in
maintenance (incorrectly). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* PURESCALE *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First Fixed in v11.1 FP4M4 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.12.2018
17.12.2018
17.12.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
