Kbase P4794: Use "proutil -C mvsch" for truncating the schema area
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/01/2009 |
|
Status: Verified
GOAL:
Why and how to use proutil -C mvsch
GOAL:
How to truncate the schema area
GOAL:
How to free disc space for the schema area
GOAL:
How to use Schema Mover
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Truncating the schema area, i.e. making the schema area as small as possible, is
done using the Schema Mover utility available with the option "mvsch" of proutil.
This option is available starting with 9.1D.
You will need to truncate the BI prior to running "mvsch".
You will be asked if you have backed up your database prior to the schema moving
executing; your database will not be recoverable if any problem occurs during the
schema move operation.
After running:
proutil <dbname> -C mvsch
the extents from the schema area have been renamed so they belong to area "Old Default Area" and a new "Schema Area" (Area 6) has been built with the schema data only. The area "Old Default Area" has its number corresponding to the first unused data area (starting at Area 7).
After mvsch has completed, the indexes for the schema area should be checked for integrity. Please see Solution P109985 for further information.
If the area "Old Default area" still contains a user table, then you will use:
proutil <dbname> -C tablemove <table_name>"<table_area>" "<index_area>"
to move away its data.
After removing all user data from the "Old Default area", you can run:
proutil <dbname> -C truncate area "Old Default area"
prostrct remove <dbname> d "Old Default Area"
to suppress the area generated by the Schema Mover.
WARNING: Data not moved prior to area truncation will be lost.
You are advised to update the <dbname>.st file by running:
prostrct list <dbname>
The Schema Mover utility should be used for all databases resulting from a "conv89"