|
Problem IC71777
|
Status: Closed |
IN A DPF ENVIRONMENT, FCM SESSIONS THAT WERE ALLOCATED WHEN DB2AUDIT COMMAND IS INVOKED WERE NEVER RELEASED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In a DPF environment, when db2audit command is invoked (e.g.
db2audit start/stop/etc), it need to update the audit setting at
other nodes.
FCM Sessions are allocated for the purpose of sending the audit
request to other nodes. However, after it finishes updating the
audit setting on other nodes, the FCM sessions that were
allocated are never released. |
| Problem Summary: |
Problem Description:
IN A DPF ENVIRONMENT, FCM SESSIONS THAT WERE ALLOCATED WHEN
DB2AUDIT COMMAND IS INVOKED WERE NEVER RELEASED
Problem Summary:
In a DPF environment, when db2audit command is invoked (e.g.
db2audit start/stop/etc), it need to update the audit setting at
other nodes.
FCM Sessions are allocated for the purpose of sending the audit
request to other nodes. However, after it finishes updating the
audit setting on other nodes, the FCM sessions that were
allocated are never released. |
| Local Fix: |
disable db2audit |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in Version 9.7 Fixpack 4 |
| Workaround |
disable db2audit |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2010
29.04.2011
29.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
