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

GLOBAL SNAPSHOTS MAY CONSUME A LARGE AMOUNT OF FCM BUFFERS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In a multipartition environment, a large amount of FCM buffers 
can be consumed by large global snapshots. One example of such 
large global snapshots is, "db2 get 
snapshot for locks on <dbname> global" when there are many 
locks currently being held in the database. 
 
db2pd -fcm hwm output would show a single application 
consuming a lot of buffers
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF environments                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Global snapshots collect monitoring information from all     * 
* database partitions and aggregate the result at the          * 
* coordinating partition. FCM buffers are required to send and * 
* receive the monitoring information. The coordinating         * 
* partition can consume a large number of FCM buffers          * 
* equivalent to the size of the entire snapshot result.  If    * 
* the database manager runs out of FCM buffers then node       * 
* failure is invoked to remedy the situation. This could lead  * 
* to applications receiving -1229 errors or losing connection  * 
* to the database.                                             * 
*                                                              * 
* Note that monitoring tools like db2top issue global          * 
* snapshots.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP4 or later                              * 
****************************************************************
Local Fix:
The work around of setting DB2_MAX_GLOBAL_SNAPSHOT_SIZE should 
help to prevent a single snapshot from consuming all FCM 
buffers. Multiple concurrent large snapshots would still be a 
problem though.
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
As of DB2 9.7 FP4, global snapshots will not consume a large 
 
number of FCM buffers.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC75870 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2010
25.04.2011
25.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4,
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList