Adding to what Ravi replied. I have a similar case as yourself. The quickest / cleanest way I found to take care of this is to create two new tablespaces. One will contain your problem table, the other will be empty. During a non-peak time I use the stored procedure admin_move_table to move the table to the empty tablespace. Try to avoid a busy time for your system as this will require db2 to take a longer time for the final synch. When that is complete I drop the original tablespace and recreate it as an empty tablespace (frees up the storage) and it is ready for the next reorg. I have had this running for a year or so without any issue (scripted so no manual intervention). Best of luck!