DB2 - Problem description
| Problem IC80672 | Status: Closed |
DB2 INSPECT NOT CHECKING ALL PAGES FOR OBJECTS IN DROP-PENDING/UNAVAILABLE STATE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 6. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 9.7 Fix Pack 6. | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84285 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.01.2012 11.06.2012 11.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|