DB2 - Problem description
Problem IT30810 | Status: Closed |
DB2DART DETECTS ERRORS AFTER UPGRADING | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
If tablespaces were created prior to V10 after upgrading to V11.1 Fixpack 4 db2dart may detect following type Errors Error: Unable to determine pool relative page number for obj rel page 15871 (Obj ID:260, Pool ID:0) due to rc 0x84020019 Error: Unable to read pool page 0, object page 15871, from pool 0, due to rc 0x84020019 Error: parent pool 0, object ID 260, object type Data. Error: extent map anchor page of object is 128272. Error: Unable to determine pool relative page number for obj rel page 12873 (Obj ID:260, Pool ID:0) due to rc 0x84020019 Error: Unable to read pool page 0, object page 12873, from pool 0, due to rc 0x84020019 Error: parent pool 0, object ID 260, object type Data. Error: extent map anchor page of object is 128272. Error: Overflow record (Object Page: 111, Slot: 8) is pointing to deleted row (Object Page: 582, Slot: 4) Error: in page 111, pool page 137207, of Object 260, in tablespace 0. Error: Page data will be dumped to report. db2dart in v11.1m4fp4 is now able to detect an orphan pointer or overflow record. However it causes a such false positive error against those tablespaces created prior to v10. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1.4.5 or later * **************************************************************** | |
Local Fix: | |
Run reorg table command to remove pointer records. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT29127 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.10.2019 31.10.2019 04.11.2019 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |