|
Problem IC93932
|
Status: Closed |
DB2 INSPECT: SPACE MAP PAGE INVALID PAGE STATES FOR EXTENT AT LO CATION <NNNN> IN THE SPACE MAP PAGE, EXTENT CONTAINS USED AND NO |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
db2 inspect may falsely report the following problem in the
formatted inspect file:
Error: Space Map Page invalid page states for extent at
location <NNNN> in the space map page, extent contains used and
not exist pages.
This can happen if you have issued a REORG INDEX(ES) with the
RECLAIM EXTENTS option. If the RECLAIM EXTENTS reclaimed a full
extent right at the end of an index SMP page (ie the next SMP
page is the first page of a new extent), or reclaimed the very
last extent in the index object, then db2inspect incorrectly
thinks that these 'Not Exist' pages exist in the same extent as
used pages and it reports the error.
There is in fact nothing wrong with the index object. However,
if you see this message, db2support should be engaged to ensure
that you indeed have a false alarm.
A sample inspect output file for a 16k page:
Database phase start.
Tablespace phase start. Tablespace ID: 33
Table phase start (ID Signed: 313, Unsigned: 313;
Tablespace ID: 32) :
Index phase start. Object: 312 Tablespace: 33
Error: In page 48771, physical page 48771 of object 312
in tablespace 33, pagesize 16384.
Error: Hexadecimal dump of page contents.
0000 *3000D03F 83BE0000 0005012A 21000000*
*0...............*
0010 *83BE0000 38010000 00000000 1F960900*
*....8...........*
0020 *37A27D3E C6290000 E3F9BFF9 AC41971F*
*7............A..*
0030 *50004630 10020001 803F803F 00000000*
*P.F0............*
0040 *00000000 00000000 00000000 00000000*
*................*
...
3FD0 *04040404 04040404 04040404 04040404*
*................*
3FE0 *04040404 04040404 04040404 04040404*
*................*
3FF0 *04040404 04040404 04040404 04040404*
*................*
Error: Space Map Page invalid page states for extent at
location 16255 in the space map page, extent contains used and
not exist pages.
Index phase end.
Table phase end. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* First fixed in Version 10.1 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 Version 10.1 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC93957
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.07.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
