timmzzz 060000RTR7 Visits (3342)
Customer X experienced Partition-By Growth (PBG) size increase with APPEND YES. Assuming the data is sparsely distributed across the PBG partitions. The following ONLINE REORG redistributed the data to the first 3 partitions. However, after the SWITCH PHASE, concurrent SQL would still append data to the last partition, leaving many partitions empty in between.
KevinHarrison 1000005N52 Visits (2928)
There are some recent REORG issues that you should be aware of, but they do not affect directory or catalog REORGs.
PM69637 - Lost data on REORG if table has OBID=1. This defect applies to V9 also.
PM62449 - Lost data on REORG if table has OBID=1 in a segmented tablespace. V10 only.
PM73000 - Incorrect rows discarded with REORG DISCARD based on boolean logic conditions. V10 only.
PM68133 - REORG of an RRF PBG with growth of a new partition during the REORG and with zparm SPRMRRF set to DISABLE.
PM69073 - Same scenario as PM68133 but in addition requires that the REORG be materializing a pending alter.
PM61976 - REORG loads data into wrong partition if using SORTDATA NO (which is not the default). Caused by PE APAR PM44475.
PM66874 - Not specifically a REORG issue, but could occur during extend processing for REORG of LOB data.
PM63324 - REORG of multiple partitions of a compressed PBG tablespace can result in rows being compressed incorrectly
KevinHarrison 1000005N52 Visits (2818)
LOB integrity abend during REORG of DBD01. Fix - PM66874,
Issue with catalog/directory space growth. FIX - PM64226 resolve for LOBs only!
For the base SPT01 growth Fix in separate APAR PM74659 not available - this will take some time!
Unformatted pages in SYSDBDXA directory LOB resulting in abends. No broken LOB data. REORG of tablespace to correct. APAR PM64226 to resolve.
Directory LOB extend failure. Fixed with APAR PM66874
REORG abend. Broken aux index. Fixed with APAR PM68842
timmzzz 060000RTR7 Visits (2258)
Setting the zparm SPRMRRF to DISABLE will prevent the conversion of pagesets from basic row format (BRF) to reordered row format (RRF), but does not convert pagesets back to BRF format.
If a REORG utility is run against a Partition-by-growth (PBG) table space that is currently in RRF format, it is possible that the PBG tablespace needs to grow a new partition during the REORG. Since the previous partitions are RRF, the new partition should be RRF in spite of the current zparm setting. Due to a code defect, the new partition is created as BRF and it can result in a mix of BRF and RRF data within the partition. This mix of row formats in a single partition should never occur.
This problem can occur in both DB2 10 CM and NFM.
Two APARs have been opened to address this issue.
APAR PM68133 is created to ensures that PBG partitions that are created during REORG will be in the correct format.
An exception is when REORG of a PBG pageset is also materializing pending alters in DB2 10 NFM. APAR PM69073 is created to correct this scenario as well.
PM68133: MIXED ROW FORMATS WAS MADE BY REORG WHEN PBG GROW
PM69073: ABEND04E RC00C90101 DSNIRLPG DURING REORG OF A PBG WITH PENDING ALTER MATE