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

DURING VIEW REGENERATION , DROPPING OF STATISTICS DON'T SET
STATISTICS_PROFILE COLUMN OF SYSTABLES CATALOG TABLE TO NULL.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The upgrade code was trying to construct runstats profile 
command checking for NULLability 
of statistics_profile column. But in reality , the runstats 
profile is deleted via view regeneration code. 
 
Simple repro script to see this behavior : 
 
In v97 , 
 
create db test 
connect to test 
create table t(c1 int, c2 int, c3 int) 
insert into t values(1,1,1) 
create view v as select * from t 
alter view v enable query optimization 
runstats on table samadesa.v WITH DISTRIBUTION ON COLUMNS(c1,c2) 
set profile 
select name , creator, substr(statistics_profile,1,50) from 
sysibm.systables where name ='V' 
alter view v disable  query optimization 
alter table t drop column c2 
select name , creator, substr(statistics_profile,1,50) from 
sysibm.systables where name ='V' 
connect reset 
 
db2cat -d test -p table -n V -s SAMADESA -t|egrep "^Table:|^ 
Stats Profile Offset"|gnugrep -B1 ": 0" 
 
hotel85:/home/hotel85/samadesa> |^ Stats Profile Offset"|gnugrep 
-B1 ": 0"   < 
 
DB2 Version 9.7, 5622-044 (c) Copyright IBM Corp. 2009 
Licensed Material - Program Property of IBM 
IBM DATABASE 2 Catalog Analysis and Repair Tool 
 
Please use single quote for delimited name 
 
Connecting to the Database. 
Connect to Database Successful. 
Bind was Successful. 
Table: SAMADESA.V   (VIEW) 
 Stats Profile Offset      : 0 
 
Now upgrade to v10 and you will get a trap in the same function 
while constructing runstats command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher.                                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.11.2013
23.09.2014
23.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList