|
Problem IC85279
|
Status: Closed |
DB2 private memory leak occurs when monitoring the host status in pureScale |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Private memory is leaked in the DB2 server process when
monitoring the overall status of a pureScale instance. The main
interfaces impacted are :
DB2_GET_CLUSTER_HOST_STATE table function
DB2_CLUSTER_HOST_STATE administrative view
DB2_INSTANCE_ALERTS administrative view
db2 list instance CLP command
For example, the db2 list instance command may leak 200K on each
invocation.
The following interfaces are also impacted, but the amount of
leaked memory is negligible due to the information retrieved:
DB2_GET_INSTANCE_INFO table function
DB2_MEMBER administrative view
DB2_CF administrative view
Continuously increasing private memory usage by the db2sysc
process is evidence this problem may be occuring. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V10 GA PureScale users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10 FP1 *
**************************************************************** |
| Local Fix: |
Use the alternative standalone command:
db2instance -list |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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 |
First fixed in DB2 V10 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.07.2012
02.11.2012
02.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
