DB2 - Problembeschreibung
Problem IC79401 | Status: Geschlossen |
MAXOFFLINEREORGTABLESIZE IS LIMITED TO 4194303 (DEC) KB | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.10.2011 06.06.2012 06.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |