Kbase P26677: Under what circumstances should Progress-to-ORACLE Utility b
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/06/2003 |
|
Status: Unverified
GOAL:
Under what circumstances should Progress-to-ORACLE Utility be used in comparison to the Progress-to-ORACLE Incremental Schema Migration Utility?
FACT(s) (Environment):
Oracle DataServer
FIX:
If you have a Progress db and want to move over to an ORACLE db environment, the Progress-to-ORACLE utility allows you to migrate a Progress database to an ORACLE database. While the DataServer typically makes an ORACLE database conform to a Progress database, this utility provides compatibility in the opposite direction. It copies an existing Progress database schema into a target ORACLE database.
Once the ORACLE database has been created, there is never a reason to redo this task again unless you are trying to maintain both (Progress and Oracl) environments together.
If you have both a Progress db and Oracle db environment, the Incremental Schema Migration utility allows you to migrate schema changes from Progress to an ORACLE database. For example, in the process of developing an application in Progress that you will migrate to ORACLE, you might want to make and test schema changes in the Progress database that you want reflected in the ORACLE database. The utility reads a Progress delta.df file that has been created using the standard incremental dump procedure and creates a delta.sql file that contains the SQL DDL for making the changes and a delta.df file. You can then load the delta.df file into the schema holder. You can then apply the delta.sql file to the ORACLE instance to complete the migration process.
However, if you're changes are very minor and you do them in ORACLE, then it's acceptable to run the migration utility again each time a schema change is made to your progress db.