Status: Verified
GOAL:
How to migrate database from any Progress version to OpenEdge 10
GOAL:
Is there a utility to convert a version 9 database to version 10 ?
GOAL:
What is proutil conv910 ?
GOAL:
How to use conv910 ?
GOAL:
One of the ways to convert a V9 database to V10: conv910
GOAL:
How to migrate a database from Progress 9 to OpenEdge 10
GOAL:
How to migrate database from Progress 6.x to OpenEdge 10.x
GOAL:
How to migrate database from Progress 7.x to OpenEdge 10.x
GOAL:
How to migrate database from Progress 8.x to OpenEdge 10.x
GOAL:
How to migrate from any Progress version to OpenEdge Release 10?
GOAL:
Considerations when migrating to OpenEdge Release 10
GOAL:
How to migrate from Progress version 8.x to OpenEdge Release 10?
GOAL:
How to migrate from Progress version 9.x to OpenEdge Release 10?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
For the database:
1) Always have a valid backup of the database before start this.
2) If you are migrating from Progress 7 or lower, is required to convet the database to version 8. See solutions 16610 and 20271 for instructions on how to do this
3) If you are migration from Progress 8 and your database is in single-volume, is required to convert to multi-volume database. See solution 18435 for instructions on how to do this.
3) Truncate the BI file using Progress 9:
proutil <db-name> -C truncate bi
4) Run proutil <db> -C conv910 using OpenEdge 10.
This should take about under 5 minute regardless of database size.
5) Backup the new database.
After performing these steps consider modify the database structure/schema to make use of the new database features offered and to review the database startup parameters that helps achieving a optimal performance.
a) Planning Storage Areas, i.e., not to have all tables and indexes in the "Schema Area".
b) A "proutil <db> -C tabanalys" will tell you the average size of the records in each table, from which you can plan the optimal number of records per block for the tables in your database structure file (.st).
c) The areas are added to an existing database using "prostrct add <db> <db.st>", then tables and indexes can be moved to newly planned Storage Areas with "proutil db -C tablemove <table> <index>"
d) The proutil utility has an option "-C mvsch" which allows to the reducing of the schema area to a minimal size.
Alternatively, the database can be migrated using an ASCII dump and load to migrate from any version directly to OpenEdge 10.x.
For the Application:
Recompile the entire application code. Note that a number of 4GL statements are being deprecated.
Make sure to test the application under OpenEdge 10.x to ensure everything still works as expected.
After these steps, it is highly recommended to review the application code and modify as required to replace deprecated statements with alternatives to prevent major migration issues in the future.
It is also recommended to review the new features and technology and implement those where applicable. For assistance on how to get the most out of the new OpenEdge 10 features, it is recommended to contact Progress Professional Services.
The following should also be taken into consideration when migrating:
- Not all OS platforms supported in earlier versions are supported in OpenEdge 10.
The OS may no longer be supported by it's vendor, or OS issues may prevent OpenEdge 10 from running correctly (as is the case with SCO OpenServer).
Please check with the Sales department which OS platforms are supported and which would be the preferred OS to move to if required.
- Increase in r-code size. R-code segments now use 32-bit offsets as opposed to the 16-bit offsets of previous releases.
This eliminates a number of practical limits for larger procedures, but it also has the side-effect of increasing the r-code size by up to 45 % depending on the contents of the procedure.
The following features have been removed either due to product retirement or due to external factors:
- SQL89 support
- Report Builder (Report Engine is still present to maintain backwards compatibility)
- ActiveX Proxy (due to Microsoft losing the Java lawsuit we may no longer distribute the required Microsoft components)