Uninstalling interim fixes and fix packs
- Stop each server on the base node using stopServer.sh
- Set the JAVA_HOME environment variable
- Verify interim fix information
- Verify fix pack information
- Run versionInfo to verify the fix and version level.
- Stop all Java processes
- Remove the highest level interim fix or fix pack from the base node using either the updateWizard or the updateSilent command.
For example, to uninstall the was50_fp2_win fix pack:cd /opt/WebSphere/AppServer/update ./updateSilent -fixpack \ -installDir "/opt/WebSphere/AppServer" \ -skipIHS \ -fixpackDir "/opt/WebSphere/AppServer/update/fixpacks" \ -uninstall \ -fixpackID was50_fp2_win
- Restart each server on the node with the startServer command.
- Verify that the node is online and functioning correctly.
- Does the interim fix or fix pack appear in the wizard panel that lists applied interim fixes, or the panel that lists applied fix packs? If so, the interim fix or fix pack is installed.
- Does the interim fix or fix pack appear in the wizard panel that lists installable interim fixes, or the panel that lists installable fix packs? If so, the interim fix or fix pack is uninstalled.
- Are there [fixID].efix or [fix packID].ptf files in...$WAS_HOME/properties/version/version...or [fixID].efixApplied, [fixID].efixDriver, [fix packID].ptfApplied, and [fix packID].ptfDriver files in...$WAS_HOME/properties/version/history
- Do the product version and history reports show the interim fix or fix pack as installed or removed?
- Does collecting interim fix information and update state show that the interim fix is installed or removed?
- Does collecting fix pack information and update state show that the fix pack is installed or removed?
- You can also run the installation verification tool on the node to verify that the node is operational.