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

REORGCHK CAN RETURN INCORRECT VALUES FOR LEAF_RECSIZE & NLEAF_RECSIZE
RESULT IN INCORRECT F5 & F6 VALUES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
reorgchk can return incorrect values for LEAF_RECSIZE & 
NLEAF_RECSIZE result in incorrect F5 & F6 values. 
 
The SYSPROC.REORGCHK_IX_STATS does not use the same calculation 
and therefore does not have the same issue. 
 
Issue is reproducible by creating a table with varchar column 
and performing the reorgchk. No partitioned table required.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.3.                             * 
****************************************************************
Local Fix:
Use the stored procedure version (SYSPROC.REORGCHK_IX_STATS) 
instead of the reorgchk CLP version.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is first fixed in DB2 version 10.1.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.02.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList