Was this helpful?
Space Requirements for Modify Operations
Modify operations require additional working disk space because a new version of the table must be built before the old table can be removed. In most cases, modify operations require about two or three times more space than the original table size. This is only an approximation; the amount of disk space actually needed can vary.
The free disk space is also required during modify to relocate and modify to reorganize operations.
For information about relocating and changing the location of storage structures, see the Modifying Storage Structures topic in online help for VDBA. For details on the DBA use of these operations, see Techniques for Moving a Table to a New Location on page 84.
In SQL, you can accomplish these tasks with the MODIFY TO REORGANIZE and MODIFY TO RELOCATE statements. For more information, see the SQL Reference Guide.
The maintain_locations privilege is needed to perform the operation on location objects in VDBA or to issue the MODIFY LOCATION statement in SQL. The maintain_locations privilege allows users to do the following:
Control the allocation of disk space
Create new locations or allow new locations to be created
Modify or remove existing locations
Temporary files are created in both the data and work locations. For example, usermod copies data between II_DATABASE and II_WORK before replacing the original table.
WARNING!  Before running usermod or MODIFY, make sure there is sufficient space in the II_DATABASE and II_WORK locations to store multiple copies of the table.
Last modified date: 04/03/2024