Kbase P158323: How to migrate Dynamics to OpenEdge 10.2B?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/02/2010 |
|
Status: Verified
GOAL:
How to migrate Dynamics to OpenEdge 10.2B?
GOAL:
What is the Dynamics migration strategy for 10.2B?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
Dynamics
FIX:
This is documented in the 10.2B release note OE001779976, and is as follows:
Note: OE00177976 Type: Product Notice
Migrating Progress Dynamics to Release 10.2B
---------------------------------
Migrating Progress Dynamics to Release 10.2B:
-------------------------------------------
Before attempting any migration, convert the physical database to Release 10.2B, using the proutil command. PSC recommends making a backup at this time.
Before migrating to Release 10.2B, Progress Dynamics customers currently using Version 2.1B must upgrade to Version 2.1B02. The following steps are the only
supported path to migrate a Version 2.1B Repository to OpenEdge 10.2B:
- Ensure the Repository is upgraded to Version 2.1B02 (db version: 020030). The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate21Setup.
- Running the DCU from this shortcut upgrades the Repository from Version 2.1B02 to Release 10.2B.
To migrate from Release 10.0B05 to Release 10.2B, follow these steps:
- Ensure the Repository is upgraded to Release 10.0B05 (db version: 100005). The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate100Setup.
- Running the DCU from this shortcut upgrades the Repository from Release 10.0B05 to Release 10.2B.
To migrate from Release 10.1A02 to Release 10.2B, follow these steps:
- Ensure the Repository is upgraded to Release 10.1A02 (db version: 101002). The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101ASetup.
- Running the DCU from this shortcut upgrades the Repository from Release 10.1A02 to Release 10.2B.
To migrate from Release 10.1B03 to Release 10.2B, follow these steps:
- Ensure the Repository is upgraded to Release 10.1B03 (db version: 101101). The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101BSetup.
- Running the DCU from this shortcut upgrades the Repository from Release 10.1B03 to Release 10.2B.
To migrate from Release 10.1C to Release 10.2B, follow these steps:
- Ensure the Repository is upgraded to Release 10.1C (db version: 101201). The migration does not work properly on earlier versions of the Repository. The
migration will also work for service packs 1 and 2.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101CSetup.
- Running the DCU from this shortcut upgrades the Repository from Release 10.1C to Release 10.2B.
To migrate from Release 10.2A to Release 10.2B, follow these steps:
- There were no updates made to the Repository between 10.2A and 10.2B, and so no migration is necessary.