We want to reorg our files to reclaim deleted record space. Since for High Availability, all our files our journaled, we run RGZPFM with ALWCANCEL(*YES) to minimize planned downtime reorgs. If journal receivers take up more space than the amount of storage we save from reclaiming deleted record space, then there really is no point in the RGZPFM with ALWCANCEL(*YES), is there?
If journal receivers take up more space than the amount of storage we save from reclaiming deleted record space, then there really is no point in the RGZPFM with ALWCANCEL(*YES), is there?
First, there probably shouldn't be any significant recovery of deleted space. As CharlieBrowne mentioned, the files (probably) should have the REUSTDLT(*YES) attribute set so there wouldn't be much of anything to recover in terms of space.
Next, the purpose of ALWCANCEL(*YES) is to enable a "Cancel" capability (along with a potential "Restart where you left off" capability). The journaling is what allows this to work.
Also, especially in a HA environment, the relaxation for LOCK(*EXCL) when ALWCANCEL(*YES) is used might be much more important than any space savings.
Finally, without the journaling, the physical reorganization is apparently done in temporary database objects. Those would take up space just as journal receivers do while the reorg is running.
Overall, it's hard to see how a comparison of recovered deleted record space and journal receiver size is related.
Tom
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
Discuss This Question: 2  Replies