Possible corrupted data pages due to pseudo-delete processing introduced for Universal table space (UTS) in DB2 10 NFM
timmzzz 060000RTR7 Visits (2151)
A table that exists in a PBG table space is altered, e.g. to add a new column or alter a column. An SQL update is then performed on an existing row. The update will change the version for the row to the new version of the table. At this point the version information for the new table format must be stored in the pageset in a system page if it doesn't already exist. If the partition is full there may not be room to allocate a set of system pages within the partition and the row must be moved to another partition instead. A defect in this scenario results in corrupted data pages in the original partition.
APAR PM68895 is created to address this problem, which can occur in DB2 10 NFM only due to pseudo-delete processing introduced for UTS table spaces in DB2 10 NFM.
PM68895 : FOR UTS PBG TABLESPACE ABEND04E RC00C90105 DSNIREPR ERQUAL0C32 DUE TO CORRUPTED IDMAPS + VARIOUS OTHER ABENDS