home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65725 Status: Geschlossen

RUNSTATS MAY UPDATE HIGH2KEY WITH NULL VALUE, IF THERE ARE MANY DIFFERENT
LONG VALUES WITH SAME FIRST 32 BYTES IN A COLUMN.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Here is the summary on the update high2key with NULL value 
issue: 
--------------------------- 
create table test(i int, c char(50)); 
insert into test(i) values 1; 
insert into test values(2, 
'0123456789112345678921234567893122222'); 
insert into test values(3, 
'0123456789112345678921234567893123333'); 
insert into test values(4, 
'0123456789112345678921234567893124444'); 
insert into test values(5, 
'0123456789112345678921234567893125555'); 
select c from test order by c desc; 
select colcard, substr(high2key,1,40), substr(low2key,1,40) from 
syscat.columns where tabname='TEST'; 
runstats on table schema.test; 
select colcard, substr(high2key,1,40), substr(low2key,1,40) from 
syscat.columns where tabname='TEST'; 
When trying to update the column statistics collected by db2look 
with -m option, it fails with SQL1227N. 
UPDATE SYSSTAT.COLUMNS SET COLCARD=2, NUMNULLS=1, SUB_COUNT=-1, 
SUB_DELIM_LENGTH=-1, HIGH2KEY='', 
LOW2KEY='012345678911234567892123456789312', AVGCOLLEN=51 WHERE 
COLNAME = 'C' AND TABNAME = 'TEST'; 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1227N  The catalog statistic "" for column "HIGH2KEY" is out 
of range for its target column, has an invalid format, or is 
inconsistent in relation to some other statistic. Reason Code = 
"3".  SQLSTATE=23521 
The update should proceed successfully.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 2.                            * 
****************************************************************
Local-Fix:
Not available.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.01.2010
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList