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

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

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* move to v105 fp7                                             * 
****************************************************************
Local Fix:


Solution


v105 fp7


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.04.2015
21.01.2016
21.01.2016


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.5.0.7

FixList