You can use the Update Installer for WebSphere® Software to uninstall interim
fixes and fix packs, collectively known as maintenance packages. You
can run it on all platforms in silent mode with a response file.
Before you begin
- Ensure that you have version 7.0.0.4 or higher of the Update Installer
for WebSphere Software
installed on your system.
- Review the topic Feature pack maintenance prerequisites.
- Ensure that you are uninstalling maintenance from an i5/OS®, Linux®, UNIX®, or Windows® system, and that you want to uninstall
in silent mode with a response file. For alternative uninstallation
procedures, click the following links:
Procedure
- Log on to the operating system.

On Linux and UNIX platforms: In addition,
verify that the umask setting is 0022.
To verify the umask
setting, type the following command: umask.
To
set the umask setting to 0022, type the following command: umask
0022
- Change directories to the Update Installer directory. The Update Installer directory is located in one of the following
locations, depending on the operating system that you are using:
On AIX® platforms: /usr/IBM/WebSphere/UpdateInstaller
On i5/OS platforms: /QIBM/ProdData/WebSphere/UpdateInstaller/V7/UPDI


On HP-UX, Linux and Solaris platforms: /opt/IBM/WebSphere/UpdateInstaller
On Windows platforms: C:\Program
Files\IBM\WebSphere\UpdateInstaller
Uninstall the interim fix on each server node in a cell before
uninstalling the maintenance package from the deployment manager node.
- Create a response file by copying the
default uninstall.txt file supplied with the
Update Installer. The file is located by default in the
following directory:
/usr/IBM/WebSphere/UpdateInstaller/responsefiles
/QIBM/ProdData/WebSphere/UpdateInstaller/V7/UPDI/responsefiles


/opt/IBM/WebSphere/UpdateInstaller/responsefiles
C:\Program Files\IBM\WebSphere\UpdateInstaller\responsefiles
- Edit and save your copy of the response file. You
can edit any portion of the response file, but be sure to specify
the following options:
For more information about the uninstall.txt file,
see the uninstall.txt topic in the WebSphere Application Server Network Deployment
documentation.
- Type the update command for your platform,
specifying the following attributes and the location of your response
file:
Important: Do not start multiple copies of the Update
Installer at one time. Running more than one instance of the Update
Installer at a time is not supported and can produce unpredictable
results, which might include a failed or faulty update.
For
more information about the update command, see
the update command topic in the WebSphere Application Server Network Deployment
documentation.
Results
If this log file contains the string INSTCONFSUCCESS
on the last line, then the update was successful. Other terms such
as INSTCONFPARTIALSUCCESS or INSTCONFFAILED can occur on other lines
within the file, or even on the last line, but if INSTCONFSUCCESS
is included in the last line, the update was successful. If the string
INSTCONFPARTIALSUCCESS or INSTCONFFAILED appears in the last line
of the file without INSTCONFSUCCESS, problems were detected during
the update. INSTCONFPARTIALSUCCESS indicates that the update completed
but errors were generated; INSTCONFFAILED, that the update failed
completely. In either case, the log file provides information to troubleshoot
the problems.
What to do next
If an interim fix involved one or more EAR files, the
deployed EAR files will not be automatically downgraded. This is an
extra manual step that is described in the interim fix readme file.
Any
deployed feature pack enterprise applications (widget EARs) will not
be uninstalled automatically. Each fix pack has documentation on how
this should be handled.