Kbase P3305: Is it necessary to dump and load A database when changing platforms
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  03/10/2009 |
|
Status: Verified
GOAL:
Is it necessary to dump and load a database when changing platform
GOAL:
Is it necessary to dump and load when changing OS
GOAL:
Is it necessary to dump and load when changing platform Involving Different Progress Media ID
GOAL:
What are the guidelines for database migration involving different Progress Media IDs
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
The general rule for migrating a Progress database from a platform to another platform a dump and load is required.
However, is not need to dump and load a database when migrating from Progress for the 32-bit flavor of an operating system to the 64-bit flavor of the same operating system.
To date, this means that there is no need for dump and load in the following scenarios:
FROM TO
------------------------------- -------------------------------
V8.X HP-UX 10.20 32-Bit V8.3X HP-UX 11 32-Bit
V9.X HP-UX 11 32-Bit V9.1X HP-UX 11 64-Bit
V9.X Solaris 32-Bit V9.1X Solaris 64-Bit
There is no need for a dump and load in the following scenarios either, but because a version change is involved, the database must be converted to version 9 using 'proutil -C conv89' on the target platform.
FROM TO
------------------------------- -------------------------------
V8.X HP-UX 10.20 32-Bit V9.X HP-UX 11 32-Bit
V8.X HP-UX 10.20 32-Bit V9.1X HP-UX 11 64-Bit
V8.3X HP-UX 11 32-Bit V9.1X HP-UX 11 64-Bit
V8.X Solaris 32-Bit V9.1X Solaris 64-Bit
Use 'proutil -C dbanalys' on the original and the new installation to compare the number of records in each table and always have a valid backup of the database before you start the migration process.