Kbase P35844: How does prostrct convert work ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/16/2009 |
|
Status: Verified
GOAL:
How does prostrct convert work ?
GOAL:
How much working space is required when running prostrct convert?
GOAL:
Does the prostrct convert routine create a second copy of the database or is the conversion done in situ ?
FACT(s) (Environment):
Progress 8.x
All Supported Operating Systems
OpenEdge Category: Database
FIX:
The prostrct convert utility will convert a Version 8 single-volume database to a multi-volume database. The utility writes to the .db file to update the database schema.
The advantage of using this strategy is when there is not enough disk space for the single-volume and multi-volume database to co-exist, the same single-volume database is effectively converted to a multi-volume database.
The disadvantage of this conversion strategy is that should this method fail or if this method is interrupted mid- execution, the database is likely to be damaged. For example, the bi reaching the 2GB limit, or the .db file very near to the 2GB limit so that during the conversion, when the .db is being written to, the limit is reached. If this is the case, alternative conversion methodologies will need to be considered. It is therefore imperative that there is a verified backup of the single-volume database before hand.
The steps to execute this conversion are:
1. Truncate the before-image file.
$ proutil dbname -C truncate bi -G 0
2. Back up and verify the current database.
For example: use the probkup utility and then run the prorest with ?vf to verify the backup:
$ probkup dbname \\server-name\shared-resource-pathname\dbname.bak
$ prorest dbname bdname.bak -vf
3. Convert the single-volume database into a single data extent multi-volume database.
$ prostrct convert dbname
Following successful completion of this exercise:
- The database.db file is renamed database.d1, a single data extent of variable length.
- The database structure file, database.db, becomes the "table of contents" for the entire database as listed in the database.st file when running ?prostrct list dbname?. This file contains a "map" of where Progress can find the extents for this database.
4. Add extents in consideration of future growth.
Determine the additional extent requirements, then define the extents in a new structure description file, newfile.st.
Then use the following command to append the extents of the .st file to the multi-volume database.
$ prostrct add dbname newfile.st
The first extent will become fixed at it's current size.
5. Backup the "new" multi-volume database.