DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

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
 

First fixed in DB2 Version 10.1 Fix Pack 1

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.06.2012
02.11.2012
02.11.2012