|
Problem IC87437
|
Status: Closed |
Use of MON_GET_CF_CMD results in the Cluster Caching Facility being restarted. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DB2 members leak management port connections when processing
MON_GET_CF_CMD . As a result no management port connections can
be established to the Cluster Caching Facility (CF) . This will
the result in the CF being killed and restarted due to the
inability of the DB2 pureScale CF monitoring routine to connect
to the management port in order to determine the health of the
CF.
This issue has been observed primarily with DB2 pureScale
instances that are monitored by Optim Performance Manager (OPM).
OPM uses MON_GET_CF_CMD to obtain information from CFs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* See APAR. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* See APAR *
**************************************************************** |
| Local Fix: |
db2stop/db2start the affected Cluster Caching Facility. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
See Error Description. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.10.2012
15.04.2013
15.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
