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

MAXOFFLINEREORGTABLESIZE IS LIMITED TO 4194303 (DEC) KB

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Currently due to an overflow while converting the value 
specified for maxOfflineReorgTableSize, the maximum possible 
size is 4194303 (dec) KB. 
 
Details: 
 
With the policy value of maxOfflineReorgTableSize="52428800", 
when multiplied with 1024, it does a 32 bit multiplication which 
leads to overflow. 
52428800 * 1024 
= dec 53687091200 
= hex C80000000 
= bin 110010000000000000000000000000000000 
only the least significant 32 bits were considered. 
 
 
The maximum value it can be set in the policy without 
overflowing 32 bit would be 
FFFFFFF(hex) divided 1024 (dec) 
= 4194303 (dec) KB   << This would be the maximum value that 
maxOfflineReorgTableSize can have 
= 3.9 GB approx
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6.                       * 
****************************************************************
Local Fix:
1) Set maxOfflineReorgTableSize to 4194303 and reorg tables 
bigger than this manually. 
 
or: 
 
2) Set the maxOfflineReorgTableSize criteria to 0, to disable 
it. It must be noted that if this is set to zero, all table 
sizes will be considered for evaluation.
available fix packs:
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
First fixed in DB2 Version 9.7 Fix Pack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.10.2011
06.06.2012
06.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList