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

REDISTRIBUTE ON MDC TABLES WITH MANY CELLS CRASHES OR PERFORMS SLOWLY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During regular processing, the redistribute utility will create 
a number of control files (CF) to record progress about the 
current redistribute operation. These files allow redistribute 
to restart after a failure, and allow the user to CONTINUE or 
ABORT the operation. 
 
Redistribute on an MDC table can create too many of these 
control files and hit one of these problems: 
1)Operating System being unable to handle the number of open 
files or 
2) Insufficient space in the file system. 
3) Slow redistribute performance due to REDISTRIBUTE keeping 
track of all the file handles on receiver partitions. This 
problem affects systems with MDC tables with many cells and a 
large number of sender partitions. 
 
During the redistribute of an MDC table, redistribute can 
generate a large number of 28 and 56 byte files in the 
redistribute control file directory. This scenario occurs when 
the redistribute utility is redistributing an MDC table, but no 
data from an MDC cell is leaving from a sender partition to a 
receiver partition.  Each MDC cell in which there is no data 
being sent, will first result in an open CF of 28 bytes, many of 
these can be opened simultaneously, because there is no 
throttling mechanism.  If too many are open, it can result in 
Operating System being unable to handle the number of files 
created.  After redistribute processing on the receiver 
partitions, the CF will eventually be closed, and the CF of 56 
bytes will stay until the end of the redistribute operation. 
Redistribute will fail to prune these unnecessary 56 byte CF 
files during processing.  This can result in too much space 
being used in the redistribute control file directory where 
these files are stored.   Due to REDISTRIBUTE having to keep 
track of these files we might hit one of the problems mentioned 
above. 
 
This problems affects a regular REDISTRIBUTE operation as well 
as a REDISTRIBUTE ABORT/CONTINUE.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* This problems affects users running regular REDISTRIBUTE     * 
* operation as well as a REDISTRIBUTE ABORT/CONTINUE.          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Redistribute on an MDC table can create too many control     * 
* files and hit this APAR.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Customer could abort the redistribute if it is slow and      * 
* continue after the instance recycle.                         * 
* Recommend to apply fixpack 3 to resolve the issue.           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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
This APAR is first fixed in Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.04.2010
27.09.2010
27.09.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList