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

INSPECT UTILITY REPORTS FALSE ERROR ON MDC TABLES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When you run INSPECT utility to check MDC (Multi Dimensional 
Clustering) tables in your database you might get false error 
reports. 
 
The error in the INSPECT report will look like following for 
example: 
 
--- 
Error: Found error type  (scan relative page 8148 EMP 258995 
with entries 12 
   after 1st non-full EMP at scan relative page 150) 
   drtbps.C dartScanExtentMapObject 1063 
--- 
 
This error says that INSPECT found multiple EMPs (Extent Map 
Pages) that do not contain the maximum number of entries. 
These holes are expected for MDC tables and therefore no error. 
 
This APAR will ensure INSPECT utility with DB2 v9.7 does not 
report this as an error. 
INSPECT utility with DB2 v10.1 and newer does not hit this 
issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 FixPack 10.                       * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 version 9.7 FixPack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.04.2014
18.11.2014
18.11.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.