DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 database instances on Windows may, over time, accumulate a 
large number of Windows handles associated with named events. 
This occurs when running a large number of LOAD FROM CURSOR 
operations.  In some cases this accumulation can contribute to 
degraded performance. 
 
Note that this problem does not occur when loading from a 
"remote fetch" cursor (i.e. where the cursor is declared using 
the DATABASE keyword), and/or when the DB2 system is a 
partitioned database environment (DPF). 
 
The number of Windows handles used by the DB2 engine process may 
be observed using the Windows Task Manager. 
 
This problem affects DB2 on Windows systems only.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************

Restart the DB2 server if the number of handles observed is 
large (more than 100,000) and performance is degraded.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 4.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC96750 IC96751 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

07.10.2013
02.06.2014
02.06.2014