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

ORPHAN ENTRIES GOT CREATED FOR STATISTICAL VIEW IN CATALOG PD

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Whenever invalid view is converted to statsview then explicitly 
re-validated (select * form v1) and dropped , orphans entries in 
catalog PD gets created and subsequent drop table will fail with 
901.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* move to v97fp7 , v101fp2                                     * 
****************************************************************
Local Fix:
The key idea is to not convert an "invalid" view to a statsview. 
Hence, before altering a view to statsview, make sure it's valid 
with the below query: 
 
"select valid from syscat.views where viewschema = <schema> and 
viewname = <name>" 
 
If valid = Y, then continue with the ALTER VIEW statement. 
Otherwise, to revalidate an invalid view, e.g. view name AB.CD, 
customer may 
 
     call SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS('view', 'AB' , 
'CD'); 
 
or 
 
    call SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS('view', NULL, 
NULL); 
 
to revalidate all views. After regular view gets out of invalid 
state, it will be safe to be converted to statview by ALTER VIEW 
statement.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
move to v97fp7 , v101fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
09.01.2013
09.01.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList