It is not necessary to dump and load the database, when starting a database created with 32bit binaries with 64-bit binaries as long as:
- The Major version is the same
- The Chipset and Operating System are the same
The reason that there is no need to dump and load within the same Progress Major release is that while the license executables are optimised for a particular bit pattern, 32 bit or 64 bit, there are no changes to the database structure between bit versions for the same Major release. Once the database is started, it is then runtime binary bound to the bit version it was started with.
If the OpenEdge Major version is different, this will require a database conversion irrespective of the bit version, as will migrating to a different platform, even if the major versions are the same.
In the Examples below, while HP-UX is used as it singularly crosses all combinations of the provisos, the same applies to all other supported Operating Systems where we supply both 32-bit and 64-bit Licenses.
Example:
10.1C 32-bit HP-UX (PA-RISC) to 10.2B 64-bit HP-UX (PA-RISC) - no conversion needed, same major version, same OS and Chipset
10.2B 32-bit HP-UX (PA-RISC) to 11.x 64-bit HP-UX (PA-RISC) – conv1011 or D&L conversion needed, different major version, same OS and Chipset .
10.2B 32-bit HP-UX (PA-RISC) to 10.2B 64-bit HP-UX (IA64) – D&L conversion needed, same major version, different Chipset (Itanium emulation is not supported).
Other Database Considerations:
1. Ensure the 64-bit or 32-bit binaries are not mixed:
- The relevant environment variables need to be directing to the appropriate binaries. This is easiest assured by running the relevant DLC/bin/proenv script for example, which will default these to those from the installation tailoring.
- The 64-bit executables must be installed into a different directory to the 32-bit binaries. In other words, do not install the new version on top of the previous version unless the previous version is no longer required.
- On UNIX platforms, do not install OpenEdge binaries to the /usr/bin when running multiple environments.
- On WINDOWS platforms, the same Major/Minor version cannot be installed on the same server until OpenEdge 11.5 and later where coexistent installation of 32-bit and 64-bit OpenEdge is supported on certified 64-bit Windows Operating Systems.
2. After-Imaging and OpenEdge Replication:
When the database is enabled for After-Imaging, it first needs to be disabled prior to opening the database in the next OpenEdge version/bit-version/Operating System.
After-Imaging between different platforms is not supported. The only supported mode of supporting After-Imaging between servers is when both servers are identical platforms, which Progress defines as being the same hardware, operating system versions as well as the same OpenEdge bit versions. As Replication is AI based, the same applies:
the source and target machines must run the same bit version of Progress and be running on the same Operating system.
