We had experienced some space issues while performing LOAD and REORG with extremely large data. In such cases we followed the below process
1. Drop the indexes
2. Perform the LOAD/REORG
3. Re-create the indexes with DEFER YES option
4. Rebuild the indexes
But it is good see that INDEXDEFER option in LOAD. With this option we can avoid index building in LOAD utility. After the LOAD we can perform rebuild indexes. With this option we can also avoid building NPI's again and again if we are performing PART level LOAD's.
Now my question is why can't we have INDEXDEFER option in REORG. Theoretically specking it was not required since we always prefer online REORG. If indexes are rebuild pending after the REORG, then it may cause outage. But practically speaking we need this option to reduce outage while handling REORG on extremely large PBG data where we are facing space issues. I mean in such case of problem scenario's we can follow the below process
1. Perform reorg with INDEXDEFER
2. Rebuild the indexes
Such that we can avoid the DROP and create of indexes.
Venkata Rama Rajesh
DB2 DBA for Z/OS