Progress 9.1B introduced the
PROUTIL Truncate Area utility to truncate a database Area for reuse by lowering the High Water Mark of the area.
Truncate Area does not delete related schema information of the objects in the truncated area. That is not the purpose of this utility.
After truncating an Area, extents can be removed with
PROSTRCT remove once all the remaining data structure are either moved to a new area using
PROUTIL tablemove or indexmove qualifiers, or once the definitions are deleted through Data Dictionary tools, as part of a dump and load area migration process
The database "Schema Area" itself cannot be truncated because it contains database meta-schema. If the database needs to be redesigned so that tables and indexes are to be removed from the Schema Area there are two ways to accomplish this:
a) Dump the database and then rebuild the database with a new .df file reflecting the new areas the database objects have been designed to be housed in. Then reload the data required.
b) Use the PROUTIL mvsch option. This utility will effectively 'truncate the Schema Area" as follows:
- Rename the current "Schema Area" to "Old Default Area",
- Create a new Schema Area
- Move the database meta schema from the old area into the new area.
This will cause the new Schema Area to be small in size as it only contains database meta schema information.
The old larger schema area is renamed to "Old Default Area", which is now no-longer contains schema objects, only application schema that was in the "schema area"
Once the remaining object content have been considered, the "Old Default Area" can be truncated and removed from the database structure.
For further information refer to the following Articles:
