Hello,
I ran an offline reorg to cluster a table that contained over100M rows. When I added a few new rows (about 1% of the table's original size), the cluster factor dropped a little bit. When I started an inplace reorg, it ran rather slowly, even though much of the table was properly organized from the previous reorg. This puzzled me, since I had guessed that the reorg would be able to skip over large portions of the table, since only a small part of it was affected by the recent inserts. Does anyone have an understanding of why an inplace reorg takes about the same to run, regardless of how much actual work needs to be done?
Thanks,
Fred
