A common customer practice is to mistakenly install the 64-bit Progress OpenEdge version on top of an AIX, HP-UX, Solaris Sparc, Windows system booted in 32-bit mode. Or 64-bit OpenEdge Service Pack against a 32-bit install and vice versa.
It is worth first verifying the current installed environment, together with checking if the Operating System is running in 64-bit or 32-bit mode. While the Progress OpenEdge 32-bit product is certified against supported 64-bit booted systems, the reverse is not true.
Media id and Port NumberEvery Progress OpenEdge product has its own product (port) and media code. These numbers must match the appropriate Operating System and will confirm the Progress OpenEdge bit version installed or the OS bit version media that has been downloaded to install.
The Table below provides this information:
HP 11 32 bit has 173 CD and 196 DVD media_id and port_number = 34
HP 11 64 bit has 175 CD and 198 DVD media_id and port_number = 36
HP Itanium2 has 186 CD and 197 DVD media_id and port_number = 40
Sun Solaris SPARC 32 bit has 157 CD and 202 DVD media_id and port_number = 11
Sun Solaris SPARC 64 bit has 182 CD and 203 DVD media_id and port_number = 39
IBM AIX POWER 32 bit has 156 CD and 200 DVD media_id and port_number = 17
IBM AIX POWER 64 bit has 187 CD and 201 DVD media_id and port_number = 37
LINUX POWERPC 64 bit has 209 CD and 210 DVD media_id and port_number = 45
LINUX AMD 64 bit has 192 CD and 205 DVD media_id and port_number = 43
LINUX INTEL 32 bit has 178 CD and 204 DVD media_id and port_number = 38
WINDOWS x86 32 bit has 146 CD and 195 DVD media_id and port_number = 31
WINDOWS x86 64 bit has 212 CD and 218 DVD media_id and port_number = 33
Where:
- "Media id" can be cross referenced by finding it in the Green Sheets that were provided within the First Commercial Shipment.
- "Port" can be verified using the following command: "$DLC/bin/showcfg $DLC/progress.cfg"
STEPS:
The install media (the first full version install or a service pack) has been downloaded from the Progress ESD site or supplied on a CD-ROM .
To determine if the install media is 64-bit or 32-bit:
1. If this is a first full version install, then on any platform where Progress OpenEdge is installed:
a. Copy the 'progress.cfg' file from the install media to a temporary directory on the local machine.
b. View the media template configuration file content by running:
$ DLC/bin/showcfg <path_to_copied_cfg>/progress.cfg
EXAMPLE 1:
Serial Number: 000015001
Control Numbers: Y8FQ? - UQN3N - JMC?N
Version Number: 11.2
Machine Class: EB
Port Number: 33
2. If this is an OpenEdge Service Pack, then view the media template configuration file on the intended server by:
a. Copy the 'progress.cfg' file from the install media to a temporary directory on the local machine.
b. View the media template configuration file content by running:
$ DLC/bin/showcfg <path_to_copied_cfg>/progress.cfg
EXAMPLE 2:
Serial Number: 000015001
Control Numbers: ?8BPH - 3PN3M - 24G?S
Version Number: 11.2.1
Machine Class: EB
Port Number: 33
c. Then confirm the current installed product that the downloaded Service Pack is intended by viewing the current configuration file content by running the same against the current progress.cfg file on the server:
$ DLC/bin/showcfg DLC/progress.cfg
EXAMPLE 3:
Serial Number: 123456789
Control Numbers: XZARS - YPH3M - 2MCY6
Version Number: 10.2B
Machine Class: EB
Port Number: 31
3. Match the Port Number with the table above to determine the Operating System and Progress OpenEdge bit version the install media is intended for.
Example 1:
The OpenEdge 11.2 install media is for a supported Windows 64-bit Operating System ( Port Number: 33 )
Example 2:
The OpenEdge 11.2.1 Service Pack install media is for a supported Windows 64-bit Operating System ( Port Number: 33 )
Example 3:
The Current Installed OpenEdge version is 10.2B for Windows 32-bit ( Port Number: 31 )
So in these examples, not only is the downloaded install media the incorrect OS bit-version (64-bit vs 32-bit) but also the incorrect OpenEdge version for the current installation on this server (11.2 vs 10.2B).
