|
Problem IT34924
|
Status: Closed |
DB2DART AND INSPECT COMMANDS FOUND ERROR TYPE VARIABLE-LENGTH DATA AT OFFSET XXXX IS READ INCORRECTLY. THE EXPECTED OFFSET IS 0
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
After upgrading to DB2 11.5.4 or 11.5.5, db2dart and INSPECT
DATABASE
command return error like:
Column-organized object phase start. Object: 883 Tablespace: 15
Traversing COL extent map, anchor 293092.
Extent map traversal complete.
Error: In page 298, physical page 298 of object 883 in
tablespace 15, pagesize 32768.
Error: Hexadecimal dump of page contents.
0000 *3000D07F 2A010000 0005072A 0F000000* *0...............*
0010 *2A010000 73030000 00000000 00000000* *....s...........*
0020 *0F3CCE38 2F010000 8D7365A4 56935C9F* *...8.....se.V...*
0030 *02010800 D6080000 013C0000 00000000* *................*
....
7FD0 *00650074 00720069 00650062 00000000* *.e.t.r.i.e.b....*
7FE0 *00000000 00000000 00000000 00000000* *................*
7FF0 *00000000 00000000 00000000 00000000* *................*
Error: Found error type variable-length data at offset 19652 is
read incorrectly. The expected offset is 0.
Error limit reached, the rest of the object is not scanned.
There is no problem to access to table and there is no Data
integrity issue. Data pages are good
The problem is an incorrect check of the tool when we have the
first tuple not at offset 0 that can be the case in DB2 10.5. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to next fixpack DB2 11.5.6 *
**************************************************************** |
| Local Fix: |
To get rid of the error message:
rename the old table, create a new table, insert into the new
table select * from the old table.
Make sure the newly created table is working and then drop the
old table. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to next fixpack DB2 11.5.6 *
**************************************************************** |
| Comment |
Upgrade to 11.5.6 or later |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.11.2020
21.06.2021
26.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
