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

RELEASING FCM RESOURCES MAY TAKE LONGER THAN EXPECTED

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
In DPF environments, the release of FCM buffers or channels may 
take longer than expected if a large number of FCM resources are 
allocated. One possible consequence of this is 
db2stop may time out due to it taking a relatively long time to 
free fast communication manager resources. FCM is shut down 
during the final phase of db2stop. When this phase takes longer 
than the time specified by START_STOP_TIME then the node is 
forcefully terminated. Another possible consequence is 
performance slowdowns that coincide with periods when FCM 
 
automatic tuning releases resources.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.5 customers                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In DPF environments, the release of FCM buffers or           * 
* channelsmaytake longer than expected if a large number of    * 
* FCM resourcesareallocated. One possible consequence of this  * 
* isdb2stop may time out due to it taking a relatively long    * 
* timetofree fast communication manager resources. FCM is shut * 
* downduring the final phase of db2stop. When this phase       * 
* takeslongerthan the time specified by START_STOP_TIME then   * 
* the node isforcefully terminated. Another possible           * 
* consequence isperformance slowdowns that coincide with       * 
* periods when FCMautomatic tuning releases resources.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* If db2stop is timing out then increase the                   * 
* START_STOP_TIMEvaluein the database manager configuration.   * 
****************************************************************
Local Fix:
If db2stop is timing out then increase the START_STOP_TIME value 
in the database manager configuration.
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 V9.5 FP7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC70978 IC71537 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.09.2010
15.11.2010
15.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList