DB2 - Problem description
Problem IT25390 | Status: Closed |
DB2 INSPECT MIGHT INCORRECTLY REPORT OUT OF RANGE ERRORS FOR BLUTABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Db2 inspect might incorrectly report errors like the following: Column-organized object phase start. Object: 4 Tablespace: 3 Traversing COL extent map, anchor 10. Extent map traversal complete. Error: Found error type physical page 376 out of range in tablespace with 374 total pages. Error: Failed to get page 376, physical page 376 for object 4 of type x7 in tablespace 3, code x8C4D0006. Error: Found error type physical page 377 out of range in tablespace with 374 total pages. Error: Failed to get page 377, physical page 377 for object 4 of type x7 in tablespace 3, code x8C4D0006. Error: Found error type physical page 394 out of range in tablespace with 374 total pages. Error: Failed to get page 394, physical page 394 for object 4 of type x7 in tablespace 3, code x8C4D0006. Error: Found error type physical page 395 out of range in tablespace with 374 total pages. Error: Failed to get page 395, physical page 395 for object 4 of type x7 in tablespace 3, code x8C4D0006. COL Object Summary: Total Pages 92 - Used Pages 88 Column-organized object phase end. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
These messages can be safely ignored. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT25359 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.06.2018 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |