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

PAGE_FETCH_PAIRS AND AVGPARTITION_PAGE_FETCH_PAIRS STATISTICS CA NNOT BE
CLEARED BY MANUAL UPDATE IF VARCHAR2 COMPATIBILITY IS ON

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Page fetch pairs statistics are collected when DETAILED index 
statistics are collected.  In a database with varchar2 
compatibility enabled, the PAGE_FETCH_PAIRS and 
AVGPARTITION_PAGE_FETCH_PAIRS statistics cannot be cleared by 
manual update of SYSSTAT.INDEXES. 
 
Typically, users might try to clear the statistics with either a 
zero-length string or a single blank string.   In both cases, 
DB2 will return an error, either SQL0407N or SQL1227N. 
 
You might experience this problem when trying to use db2look in 
mimic mode on a database with varchar2 compatibility enabled.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 9.                    * 
****************************************************************
Local Fix:
To clear the index statistics, perform a runstats without 
DETAILED index statistics, for example, 
   RUNSTATS ON TABLE TEST.T1 WITH DISTRIBUTION AND INDEXES ALL 
 
If you have a -m db2look mimic output file you want to apply, 
1) replace the table-only runstats command with one that also 
collects basic index statistics 
2) replace PAGE_FETCH_PAIRS='' with PAGE_FETCH_PAIRS=' ' 
3) replace AVGPARTITION_PAGE_FETCH_PAIRS='' with 
AVGPARTITION_PAGE_FETCH_PAIRS=' ' 
 
For example, 
 
replace occurrences of: 
RUNSTATS ON TABLE "TEST    "."T3" ; 
    PAGE_FETCH_PAIRS='', 
    AVGPARTITION_PAGE_FETCH_PAIRS='', 
 
with: 
RUNSTATS ON TABLE "TEST    "."T3" AND INDEXES ALL ; 
    PAGE_FETCH_PAIRS=' ', 
    AVGPARTITION_PAGE_FETCH_PAIRS=' ',
available fix packs:
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
Problem was first fixed in DB2 UDB Version 9.7 FixPack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95344 IC95349 IC96244 IC97821 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2013
23.12.2013
23.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList