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

RUNSTATS USE PROFILE RESULTS IN TRAP WHEN PROFILE IS SET WITH AL L COLUMNS
+ DISTRIBUTION ON KEY COLUMNS OPTION AND WE HAVE INDEX

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DESCRIPTION: 
 
RUNSTATS USE PROFILE results in memory corruption and trap when 
we have an index created on expression column and the profile is 
set with ALL COLUMNS + DISTRIBUTION ON KEY COLUMNS option. 
 
 
Ex: 
 
create table s1.t1 (c1 int, c2 int, c3 varchar(20), c4 int) 
DB20000I  The SQL command completed successfully. 
 
create index s1.id1 on s1.t1 (c1,c2) 
DB20000I  The SQL command completed successfully. 
 
create index s1.id2 on s1.t1 (c4, upper(c3)) 
DB20000I  The SQL command completed successfully. 
 
runstats on table s1.t1 on all columns with distribution on key 
columns set profile only 
DB20000I  The RUNSTATS command completed successfully. 
 
runstats on table s1.t1 use profile 
SQL2310N  The utility could not generate statistics.  Error 
"-1224" was 
returned. 
 
 
 
WORKAROUND: 
 
Specify explicit column names instead of "ALL COLUMNS" option to 
avoid the issue
Problem Summary:
RUNSTATS USE PROFILE RESULTS IN TRAP WHEN PROFILE IS SET WITH AL 
L COLUMNS + DISTRIBUTION ON KEY COLUMNS OPTION AND WE HAVE INDEX
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2014
20.01.2016
20.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