DB2 - Problem description
| Problem IC79792 | Status: Closed |
PARTITIONED INDEX STATISTICS MAY NOT BE REPRESENTATIVE WHEN DATA PARTITION DETACH HAS OCCURRED | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
The statistics of a partitioned index may not be representative
after data partition detach occurs. The statistics stored in
syscat.indexpartitions and syscat.indexes may show
inconsistency. For example, nlevels in syscat.indexes is 0 while
none of nlevels in syscat.indexpartitions is 0.
To determine if this problem affects a particular table:
1. Collect db2cat output: db2cat -d dbname -s schema -n table -o
db2cat.out
2. Find the "Data Partitioning DESCRIPTION" section, for
example:
Data Partitioning DESCRIPTION
-----------------------------
Flags : PARTITIONED
Number partitions : 5
Number partitioning cols : 1
MAX Data Partition ID : 7
3. If "MAX Data Partition ID" is greater than "Number
partitions", the table might experience the problem. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users with table partitioning data organization * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 Fix Pack 6 * **************************************************************** | |
| Local Fix: | |
Manually update the statistics in sysstat.indexes to a non-zero value or consult DB2 support for a value to be used for the manual update. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
The problem was first fixed in Version 9.7 Fix Pack 6 | |
| Workaround | |
See Local Fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84512 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.11.2011 14.06.2012 14.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 |
|