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

DB2 INSPECT NOT CHECKING ALL PAGES FOR OBJECTS IN DROP-PENDING/UNAVAILABLE
STATE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Running INSPECT with option FOR ERROR STATE ALL is supposed to 
scan through the object even if internal state already lists 
error state. 
 
However for invalid-state DAT objects without cached TCBs (i.e. 
all such objects after a deactivation of the database) only page 
0 is checked. 
The formatted INSPECT report will show messages like following 
indicating only 1 DAT page being used. 
 
      Data phase start. Object: 123  Tablespace: 456 
      Warning: Object is known to be in error state x800. 
      Warning: Object is in drop-pending/unavailable state. 
      Warning: Proceeding through this object, errors identified 
may be due to the known state of the object. 
       Traversing DAT extent map, anchor 528. 
       Extent map traversal complete. 
       DAT Object Summary: Total Pages 1 - Used Pages 1 - Free 
Space 0 % 
      Data phase end. 
 
This APAR will ensure INSPECT is scanning all pages for objects 
in drop-pending/unavailable state if option FOR ERROR STATE ALL 
is used.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
First fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
02.11.2012
02.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList