PQ74850: A failed uninstall of multiple components in WAS5 using the updateInstaller could corrupt WebSphere AppServer installation.

APAR status
Closed as program error.

Error description
The potential for problems exists while uninstalling multiple
components using the updateInstaller (i.e., when uninstalling a
Fix Pack).  If a component fails during the uninstall,
subsequent components will report failures and are corrupted.

The symptoms for this are as follows.  Note that the log files
referenced are found in WAS_HOME/properties/version/log and
WAS_HOME/properties/version/history.
- A component reports a legitimate failure during the uninstall
  process (such as locked files.)
- Every component uninstalled thereafter reports a failure in
Local fix
the "sum ary" log file.  A side-effect of this bug is that
  the "results" section will report a different component name
  than is being processed.
- The individual component log files will report that the
  uninstall was successful, despite the failure reported in the
  summary log file.
- The backup .jar file associated with the component is deleted.
- The "ptfApplied" file will incorrectly report that the
  component has not been uninstalled, and "points" to the
  missing backup .jar file.
LOCAL FIX:ン
These problems leave very little chance for recovery.  The
customer will most likely need to reinstall WebSphere
Application Server.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server customers who   *
*                 have Java processes running when they try to *
*                 install/uninstall a fix pack that updates    *
*                 the JDK.                                     *
****************************************************************
* PROBLEM DESCRIPTION: The inability to update the JDK causes  *
*                      a "cascading failure" i.e. the          *
*                      install/uninstall of all subsequent     *
*                      components fails and the installation   *
*                      becomes corrupted. The user can neither *
*                      complete the install/uninstall, nor     *
*                      back it out.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The update installer no longer attempts to update subsequent
components when the update of the JDK fails, thereby
avoiding the "cascading failure" problem.
Problem conclusion
The WebSphere Application Server installation is not corrupted,
and the fix pack can successfully be installed/uninstalled after
correcting the original cause of failure (Java processes
running).
Temporary fix Comments
APAR information
APAR number PQ74850
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-06-03
Closed date 2003-07-08
Last modified date 2003-07-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
INSTALL          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ74850
IBM Group: Software Group
Modified date: Jul 29, 2003