Kbase P22902: Do we have to dump and reload the database when Progress bit versions are different ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/11/2005 |
|
Status: Verified
GOAL:
When upgrading to from an earlier 32-bit Progress 9.x License to a 64-bit Progress 9.x Product, is it necessary to dump and load the database?
GOAL:
When upgrading to Progress 9.1D 64-bit from a 32-bit Progress version is it necessary to dump and load the database?
GOAL:
Is it necessary to dump and load to upgrade from an earlier Progress 32-bit version to later Progress 64-bit version on Solaris 64 bit?
GOAL:
Is it necessary to dump and load to upgrade from an earlier Progress 32-bit version to later Progress 64-bit version on HP-UX 64 bit?
GOAL:
Is the database in the same structure under 32bit Progress as under 64bit Progress?
GOAL:
Do we have to dump and reload the database when Progress bit versions are different ?
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.0x
FIX:
It is not necessary to dump and load the database, but the 9.x 64-bit executables must be installed into a different directory than the 9.x 32-bit files. In other words, do not install the new version on top of the previous version.
The reason that there is no need to dump and load within the same Progress major release is that the Progress executables are optimised for a particular bit pattern, 32 or 64 bit, but there are no changes to the /*database structure*/ between bit versions for the same major release.
Please note if the Progress major version is different, this will require a datbase conversion irrespective of the bit version as will migrating to a different platform, even IF the major version is the same.
example:
9.1C 32-bit HP-UX to 9.1E 64-bit HP-UX (no conversion needed, same major version, same OS)
9.1C 32-bit HP-UX to 10.x 64-bit HP-UX (conversion needed, different major version, same OS)
9.1C 32-bit HP-UX to 9.1E 64-bit TRU64 (conversion needed, same major version, different OS)