|
Problem IT24585
|
Status: Closed |
INSERTS TO A PAGE MAY NOT RE-USE RESERVED SPACE ON A PAGE PROPERLY WHICH CAUSES NEW PAGE ALLOCATION AND OVERFLOW RECORDS
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
If there's reserved space on a page, an update to the page that
doesn't change any record lengths may cause us to not release
old reserved space properly. The consequence for this is that
any insert/update in the same transaction may cause us to
allocate new pages or create overflow records even though
there's usable space on existing pages in the table.
This is especially a problem for SYSBOOT because creation of
overflow records in this table causes dart to report false
errors. Dart would report the following error if there are
overflows on SYSBOOT.
Traversing extent map for:
OTR ID: 4
Parent object ID = 1 pool ID = 0
For all table objects in tablespace: 0
DAT extent anchor: 516, in pool: 0
Traversing extent map for object type: 0
Extent Map traversal complete.
Error: The size 0 of the tid/fid pairs array is not big
enough to have array entry 0.
Warning: Object in Object Table not found in SYSTABLES
for ObjID:1, TabspID:0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* UPGRADE TO DB2 V10.5FP10 OR HIGHER FIXPACK LEVEL *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.03.2018
17.07.2018
17.07.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
