Kbase 33305: Database Migration Involving Different Progress Media ID
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P3305
GOAL:
Database Migration Involving Different Progress Media ID
FIX:
In general, the rule for migrating a Progress database to another platform is, execute a dump and load (especially a migration to platforms that have a different byte order).
There are some specific situations where you do not need to execute the dump and load process to migrate a database.
You do not need to dump and load a database under the following situations:
FROM: TO:
V8.X HP-UX 10.20 32-Bits V8.3X HP-UX 11 32-Bits
V8.X HP-UX 10.20 32-Bits V9.X HP-UX 11 32-Bits
V8.X HP-UX 10.20 32-Bits V9.1X HP-UX 11 64-Bits
V8.3 OR V9.X HP-UX 11 32-Bits V9.1X HP-UX 11 64-Bits
V8.X OR V9.X Solaris 32-Bits V9.1C Solaris 64-Bits
Of course, when a version change is also involved, the database must be converted to Version 9 using 'proutil -C conv89' on the target platform.
Progress recommends you use the PROUTIL dbanalys on the original and the new installation to compare the number of records in each table. Always have a valid backup of the database before you start the migration process.