A fix is available
APAR status
Closed as program error.
Error description
RUNSTATS INDEX at PART level is setting DATAREPEATFACTORF=0 in SYSIBM.SYSINDEXSTATS for every index partitions, and also setting DATAREPEATFACTORF=0 in SYSIBM.SYSINDEXES for the whole partitioned index. This is causing Access Path issues. DATAREPEATFACTORF should not be zero, as stated in "SQL Reference" manual. It looks this happenes when there are empty partitions.
Local fix
Runstats the whole tablespace.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of RUNSTATS utility on a partitioned * * table space with DB2 subsystem parameters * * STATROLL=YES and STATCLUS=ENHANCED. * **************************************************************** * PROBLEM DESCRIPTION: DATAREPEATFACTORF is 0 in catalog * * table SYSIBM.SYSINDEXSTATS and * * SYSIBM.SYSINDEXES after RUNSTATS INDEX * * PART n on a non-empty partitioned * * table space with ZPARM * * STATCLUS=ENHANCED and STATROLL=YES. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A RUNSTATS INDEX PART n was run on a partitioned table space with DB2 system parameters STATCLUS=ENHANCED and STATROLL=YES. The DATAREPEATFACTORF statistic was 0 in both the SYSINDEXSTATS and SYSINDEXES catalog tables and also reported as 0 in MSGDSNU617I and MSGDSNU627I, but the table was not empty. A similar problem can occur during the LOAD, REORG or REBUILD INDEX utility when gathering inline statistics on indexes.
Problem conclusion
Code has been modified to correctly update SYSINDEXSTATS and SYSINDEXES with the value for DATAREPEATFACTOR and to report the value correctly in DSNU617I and DSNU627I. A documention change is needed in the SQL REFERENCE for catalog tables SYSINDEXES, SYSINDEXES_HIST, SYSINDEXSTATS and SYSINDEXSTATS_HIST The description for DATAREPEATFACTORF will read as follows: The anticipated number of data pages that will be touched following an index key order. This statistic is only collected when the STATCLUS subsystem parameter is set to ENHANCED. This number is -1 if statistics have not been collected. This is an updatable column.
Temporary fix
Comments
APAR Information
APAR number
PM75275
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-17
Closed date
2012-11-20
Last modified date
2013-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK83682 UK83683
Modules/Macros
DSNUSAIX DSNUSEOF DSNUSUIX DSNUSUPI
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2013