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 IC82426 Status: Closed

FCM SESSION LEAK ISSUE DURING THE STRESS RUN

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
During the stress run and as load increases, more connections 
are created, and as a result more communication sessions are 
added.  When load is reduced, these connections are removed, 
however, the associated communication session is not, resulting 
in the leak.  The message referenced below is a result of the 
connections being added to the database, and DB2 discovering the 
stale connections exist and releasing the resources allocated. 
The occurrences of this message was higher than expected: 
 
2012-03-27-00.06.13.475266+540 I1566A370            LEVEL: 
Warning 
PID     : 11075644             TID  : 2571          PROC : 
db2sysc 0 
INSTANCE: pmninst              NODE : 000 
EDUID   : 2571                 EDUNAME: db2pdbc 0 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfFastCommManager::getCommSession, probe:10 
MESSAGE : Warning, detected and freed stale comm-session.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v98fp5                                        * 
****************************************************************
Local Fix:
Solution
No more FCM session leak if customer upgrade to db2_v98fp5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.04.2012
04.07.2012
04.07.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList