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

REORGCHK DOES NOT RETURN ALL INDEXES DEFINED FOR THE SPECIFIED TABLE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
To calculate REORGCHK formula F4-F8, reorgchk calculates the 
average index record size and min key size for both leaf and 
non-leaf pages. While calculating average index record size, if 
any query failed to return any data; reorgchk stops processing 
for other indexes and moves on to next table. Reorgchk should 
continue processing for other indexes of the same table. 
 
This issue affect only the "REORGCHK" command. Under some 
circumstances, it is possible that the REORGCHK command might 
not evaluate all indexes defined for the table. 
 
If you are impacted by the issue, you can use the 
SYSPROC.REORGCHK_IX_STATS () function instead. 
 
Per example, if the command 
     db2 "REORGCHK CURRENT STATISTICS ON TABLE SAMPLE.MY_TABLE" 
 
returns only some of the indexes, you may use the function 
instead as follows: 
    db2 "CALL SYSPROC.REORGCHK_IX_STATS('T','SAMPLE.MY_TABLE')" 
 
The use of the function will return all indexes as it should.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All using REORGCHK command                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* To calculate REORGCHK formula F4-F8, reorgchk calculates the * 
* average index record size and min key size for both leaf and * 
* non-leaf pages. While calculating average index record size, * 
* if any query failed to return any data; reorgchk stops       * 
* processing for other indexes and moves on to next table.     * 
* Reorgchk should continue processing for other indexes of the * 
* same table.                                                  * 
*                                                              * 
* This issue affect only the "REORGCHK" command. Under some    * 
*                                                              * 
* circumstances, it is possible that the REORGCHK command      * 
* might                                                        * 
* not evaluate all indexes defined for the table.              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version 9.7 fixpack 5                             * 
****************************************************************
Local Fix:
Use CALL SYSPROC.REORGCHK_IX_STATS() instead of REORGCHK.
available fix packs:
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
First fixed in version 9.7 fixpack 5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC85778 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.04.2011
13.12.2011
13.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList