Did this article resolve your question/issue?



Can Proutil Truncate Area be used to delete Schema?

« Go Back


TitleCan Proutil Truncate Area be used to delete Schema?
URL NameP7866
Article Number000148324
EnvironmentProduct: Progress
Version: 9.1B, 9.1C, 9.1D, 9.1E
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
Can PROUTIL truncate area be used to delete schema?
Will truncating an area delete the related object's schema definitions?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
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:
  1. Rename the current "Schema Area" to "Old Default Area",
  2. Create a new Schema Area
  3. 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:
References to Other Documentation: 

Progress Documentation: 

OpenEdge Data Management: Database Administration, Reference, PROUTIL Utility, PROUTIL TRUNCATE AREA qualifier
Last Modified Date11/20/2020 7:22 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.