To apply a Hotfix on UNIX systems:
1. Backup the current install by taking a copy of the installation directory ($DLC) ensuring permissions are preserved.2. Before applying the Hotfix:
a. Ensure that the appropriate Service Pack Level for the hotfix is already installed.
For example: If applying Hotfix 11.5.1.016, ensure that the 11.5.1 Service Pack is already installed before applying TFIX 016.
b. Ensure that the appropriate Hotfix has been dowloaded from ESD for the current install:
Progress/OpenEdge [Major version].[Minor version].[Service Pack].[Hotfix].[OS]
For example:
- Hotfix 11.5.1.016 for Linux 64-bit OpenEdge installation: PROGRESS_OPENEDGE_11.5.1.016_LNX_X86_64.tar.gz
- Hotfix 11.5.1.016 for Linux 32-bit OpenEdge installation: PROGRESS_OPENEDGE_11.5.1.016_LNX_X86.tar.gz
If in any doubt please contact Progress Technical Support.
3. Read the hotfix README.txt file.
These are the release notes for the hotfix. Ensure any special pre/post-installation steps specific to the Hotfix being applied are followed.
4. Save the
<hotfixfile>.tar.Z file into a temporary directory.
cd to the directory where the hotfix has been saved to
$ uncompress <hotfixfile>.tar.Z
$ tar -xvf <hotfix file>.tar
Optionally, delete <hotfix file>.tar after tar extraction.
5. Change permissions by executing the following:
$ chown -R root *
$ chmod -R 4775 bin/_*
$ chmod 775 bin/_sqlsrv2
6. Shut down all running Progress/OpenEdge processes for the install environment the Hotfix is being applied to.
This includes but not exclusively: AdminServer, Databases, Ubrokers and all related cron jobs.
If OS version = AIX, run "
slibclean" to release the libraries from OS cache.
7. Ensure the DLC environment variable is the Progress/OpenEdge installation path.
For example:
$ DLC=/progress/dlc; export DLC
Replace the current OpenEdge install files / executables with the Hotfix content:
$ cp -R * $DLC
8. Change permissions as needed. These can be confirmed against the backup taken before applying the Hotfix.
To apply a Hotfix on Windows systems:
1. Backup the current install by taking a copy of the installation directory (%DLC%).
2. Before applying the Hotfix:
a. Ensure that the appropriate Service Pack Level for the hotfix is already installed.
For example: If applying Hotfix 11.5.1.016, ensure that the 11.5.1 Service Pack is already installed before applying TFIX 016.
b. Ensure that the appropriate Hotfix has been downloaded from ESD for the current install:
Progress/OpenEdge [Major version].[Minor version].[Service Pack].[Hotfix].[OS]
For example:
- Hotfix 11.5.1.016 for Windows 64-bit OpenEdge installation: PROGRESS_OPENEDGE_11.5.1.016_WIN_64.zip
- Hotfix 11.5.1.016 for Windows 32-bit OpenEdge installation: PROGRESS_OPENEDGE_11.5.1.016_WIN.zip
If in any doubt please contact Progress Technical Support.
3. Read the hotfix README.txt file.
These are the release notes for the hotfix. Ensure any special pre/post-installation steps specific to the Hotfix being applied are followed.
4. Shut down all running Progress/OpenEdge processes for the install environment the Hotfix is being applied to. Including but not exclusively: AdminService, Databases, Ubrokers and all related scheduled tasks.
5. Save the
<hotfixfile>.exe or
<hotfixfile>.zip file into a temporary directory.
- Execute the <hotfixfile>.exe (a Self-Extracting Winzip file) or extract the <hotfixfile>.zip file.
- Direct the "Unzip to folder:" to the current Progress/OpenEdge installation (%DLC%).
- Ensure that the "Overwrite files without prompting" is checked.
- Select "Unzip" to extract the files. This will overwrite the files in the current installation.
- Include the content of the 'pdbfiles' folder. For further information refer to Article What is the purpose of .PDB files?
Other Considerations:
Applying an OpenEdge Hotfix, there are no validation or verification checks. It is essentially an OS copy which replaces the file content of the current install with the new files provided. When the wrong Hotfix was applied to the current OpenEdge install, or when the new files cannot replace existing files that are currently being used by running processes, undesired consequences will arise:
