|
Problem IC87438
|
Status: Closed |
OPM pureScale monitoring command timeouts due to locked resources by GPFS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Various DB2 pureScale monitoring functions are defined to OPM.
For example, DB2_GET_CLUSTER_HOST_STATE, which retrieves
information about the cluster hosts (alerts, active/inactive) is
defined to OPM.
When it is exercised, db2 forces a gpfs information refresh on
all nodes (mmchnode -N all --gpfs_version=Default).
Since OPM's view of the world is in terms of the databases and
not the cluster, OPM can issue multiple
requests to DB2_GET_CLUSTER_HOST_STATE for many databases
concurrently. This can result in GPFS locking of cluster
resources such as the cluster configuration, ultimately leading
to possible monitor command timeouts. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 pureScale instances *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V10.1 FP2 *
**************************************************************** |
| Local Fix: |
|
| 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 |
Fixed in V10.1 FP2. |
| 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
|
|
