home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71775 Status: Closed

N A DPF ENVIRONMENT, FCM SESSIONS THAT WERE ALLOCATED WHEN DB2AUDIT COMMAND
IS INVOKED WERE NEVER RELEASED

product:
DB2 FOR LUW / DB2FORLUW / 910 - 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.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem is first fixed in Version 9.1 Fix Pack 10
Workaround
disable db2audit
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71776 IC71777 IC71884 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.10.2010
13.06.2011
13.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList