Kbase P18295: How much space is needed for a tablemove.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/11/2009 |
|
Status: Verified
GOAL:
How much space is needed to remove tables from the schema area and then truncate the schema area?
GOAL:
How much space is needed to use the proutil tablemove command and then truncate the schema area?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1x
OpenEdge 10.x
FIX:
The required free space would be equal to the current size of the database plus additional space for BI growth and ample space for AI extents if after imaging is active, but the files are not managed.
A database of 10GB would require an additional 10GB of free disk space or a total space of 20GB for the data files, as all the tables must be removed from the schema area before the truncate schema area is done or data will be lost.
Bi files can grow very large (a number of times larger than the space taken by the table and by the indexes) and after-imaging can cause a high number of after-image extent switches if it is enabled.
When there are space or time constraints, this process may be broken into to multiple sessions by only moving some tables at a time, rather than all at once. This will reduce the space requirements on the BI and AI files, reduce the transaction scope, as well as reduce the time window requirements for a single session. This will not reduce the total time it take to move all the tables nor the amount of space required for the data files.