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

LOAD WITH STATS COLLECTION MIGHT GENERATE NLEVEL VALUE AS 0 IN CERTAIN
SCENARIO FOR PARTITIONED INDEXES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The issue can be reproduced in the following scenario: 
 
1. 
create table test1( a BIGINT NOT NULL, 
                    b INTEGER NOT NULL) 
                    distribute by hash(a) 
                    partition by range (b) 
                    (PART "PART0" STARTING('1')  ENDING('10'), 
                     PART "PART1" STARTING('11') ENDING('20')); 
 
create index indx1 on sahanant.test1 (b); 
runstats on table sahanant.test1 and indexes all set profile 
only; 
load from data.del of del MESSAGES "msgfile" REPLACE into 
sahanant.test1 statistics use profile; 
 
 
select substr(indname, 1, 10), nlevels, indcard, numrids from 
syscat.indexpartitions where indname='INDX1' 
 
1          NLEVELS INDCARD              NUMRIDS 
---------- ------- -------------------- -------------------- 
INDX1            0                    3                    3 
INDX1            1                    0                    0 
 
  2 record(s) selected. 
 
 
select substr(indname, 1, 10), nlevels, indcard, numrids from 
syscat.indexes where indname='INDX1' 
 
1          NLEVELS INDCARD              NUMRIDS 
---------- ------- -------------------- -------------------- 
INDX1            0                    1                    1 
 
  1 record(s) selected. 
 
 
 
 
>cat data.del 
0,1 
1,2 
2,3
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Software                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v101 fp3                                          * 
****************************************************************
Local Fix:
Perform another statistics collection via the runstats command, 
for example, 
RUNSTATS ON TABLE sahanant.test1 USE PROFILE
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
move to v101 fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2013
03.10.2013
03.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