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 IT08330 Status: Geschlossen

MEMORY CORRUPTION DURING RUNSTATS 'UPDATE PROFILE' OPTION IF
DUPLICATE COLUMN GROUPS ARE INVOLVED.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Memory corruption during runstats 'update profile' option if 
duplicate column groups are involved 
 
runstats 'update profile' command fails with error -1224, 
generating FODC and trap file. 
 
Ex: 
 
create table s1.t1 (c1 int, c2 int, c3 varchar(122), c4 
varchar(123)); 
 
runstats on table s1.t1 on columns ((c1,c2), (c1,c2)) set 
profile only 
 
runstats on table s1.t1 on columns ((c1,c2), (c2,c1)) update 
profile only; 
SQL2310N  The utility could not generate statistics.  Error 
"-1224" was 
returned. 
 
In runstats set profile we have specified columns group (c1,c2) 
twice. When update profile also contain the same column group 
(c1,c2) it will result in memory corruption.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* move to v105 fp7                                             * 
****************************************************************
Local-Fix:
Lösung
v105 fp7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.04.2015
21.01.2016
21.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList