DB2 FOR LUW / DB2FORLUW / A50 - DB2

When a row is moved by inplace reorg and the row is page 
compressed at its new location, in the unlikely event that the 
page dictionary is recreated, the row is no longer page 
compressed and the move of the row is rolled back, the row could 
be left in a corrupted state. Subsequent access of the row can 
result in incorrect data being returned or an abend. 
 
Roll back of the move of the row may also fail. Should roll back 
fail, information will be written to the db2diag.log. Examples 
include 
 
FUNCTION: DB2 UDB, data management, sqldUndoMoveNormalRecord, 
probe:2157 
MESSAGE : ZRC=0x00002718=10008 
 
DATA #1 : String, 11 bytes 
Error code: 
DATA #2 : Hex integer, 4 bytes 
0x00002718 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00002AAAAD80327F pdLog + 0x509 
  [1] 0x00002AAAAEDFEF7B 
_Z24sqldUndoMoveNormalRecordP8sqeAgentP8SQLD_TCBiP19SQLD_MOVE_NO 
RMAL_LRP9SQLP_LSN8 + 0x1D83 
  [2] 0x00002AAAAEACA6C8 
_Z7sqldfunP8sqeAgentP8SQLD_LRHP9SQLP_LSN8s + 0x18D2 
  [3] 0x00002AAAAEC34643 
_Z8sqldmundP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0xEA9 
  [4] 0x00002AAABAB93AB2 
_Z8sqlptudoP8sqeAgent12sqlpUndoTypePmP15SQLD_RECOV_INFOP11SQLP_T 
ENTRYP8SQLP_LRHPc + 0x17C6 
  [5] 0x00002AAABAB8E543 _Z8sqlptud1P8sqeAgentm + 0x86F 
  [6] 0x00002AAABAB35E4C 
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc 
h + 0x49BA 
  [7] 0x00002AAAAEDAFEEF 
_Z20sqldOnlineTableReorgP8sqeAgenttthmittPciS1_iP9SQLP_LSN8S3_si 
+ 0x5A35 
  [8] 0x00002AAAAEDB8D7B _Z13sqldOLRInvokeP8sqeAgentPc + 0x4E9 
  [9] 0x00002AAAB5BF262A 
_Z26sqleIndCoordProcessRequestP8sqeAgent + 0xD6E 
  [10] 0x00002AAAB5C5B4FB _ZN8sqeAgent6RunEDUEv + 0x61B 
 
or 
 
FUNCTION: DB2 UDB, data management, sqldUndoMoveNormalRecord, 
probe:2182 
MESSAGE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data 
Page" 
          DIA8500C A data file error has occurred, record id is 
"". 
DATA #1 : String, 36 bytes 
Compressed record length incorrect. 
DATA #2 : String, 18 bytes 
Compressed length: 
DATA #3 : unsigned integer, 4 bytes 
4 
DATA #4 : String, 16 bytes 
Expected length: 
DATA #5 : unsigned integer, 2 bytes 
59 
DATA #6 : String, 15 bytes 
Log record LSN: 
DATA #7 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes 
0000000000056001 
DATA #8 : Hexdump, 32 bytes 
0x00002AAAD43F7580 : 018E 0200 0400 1800 150D 2001 3B00 3C00 
.......... .;.<. 
0x00002AAAD43F7590 : 0000 2D00 2100 0000 8A00 0000 0000 2100 
..-.!.........!. 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00002AAAAD80327F pdLog + 0x509 
  [1] 0x00002AAAAEDFF39F 
_Z24sqldUndoMoveNormalRecordP8sqeAgentP8SQLD_TCBiP19SQLD_MOVE_NO 
RMAL_LRP9SQLP_LSN8 + 0x21A7 
  [2] 0x00002AAAAEACA6C8 
_Z7sqldfunP8sqeAgentP8SQLD_LRHP9SQLP_LSN8s + 0x18D2 
  [3] 0x00002AAAAEC34643 
_Z8sqldmundP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0xEA9 
  [4] 0x00002AAABAB93AB2 
_Z8sqlptudoP8sqeAgent12sqlpUndoTypePmP15SQLD_RECOV_INFOP11SQLP_T 
ENTRYP8SQLP_LRHPc + 0x17C6 
  [5] 0x00002AAABAB8E543 _Z8sqlptud1P8sqeAgentm + 0x86F 
  [6] 0x00002AAABAB35E4C 
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc 
h + 0x49BA 
  [7] 0x00002AAAAEDAFEEF 
_Z20sqldOnlineTableReorgP8sqeAgenttthmittPciS1_iP9SQLP_LSN8S3_si 
+ 0x5A35 
  [8] 0x00002AAAAEDB8D7B _Z13sqldOLRInvokeP8sqeAgentPc + 0x4E9 
  [9] 0x00002AAAB5BF262A 
_Z26sqleIndCoordProcessRequestP8sqeAgent + 0xD6E

**************************************************************** 
* USERS AFFECTED:                                              * 
* INPLACE TABLE REORG                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************

Problem was first fixed in DB2 UDB Version 10.5 fix pack 6

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

14.01.2015
14.09.2015
14.09.2015