|
Problem IT32333
|
Status: Closed |
DB2MSCS.EXE CRASHES WITH TOO LONG A CLUSTER NAME
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When attempting to setup a hot-standby single-partition using
db2mscs.exe, it may crash or an error may be returned stating
that the IP name already exists.
The cause of this is specifying a cluster_name in db2mscs.cfg
that extends beyond the 15 byte limit. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows. Db2 v10.5, v11.1, v11.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v11.1 fix pack 6 *
**************************************************************** |
| Local Fix: |
Define a cluster name that is less than or equal to 15 bytes. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Windows. Db2 v10.5, v11.1, v11.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v11.1 fix pack 6 *
**************************************************************** |
| Comment |
Instead of crashing, db2mscs.exe will gracefully fail when a
cluster name is inputted beyond the allowable range. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.03.2020
14.01.2021
14.01.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
