IBM Support

PM18760: UPDATEINSTALLER MAY INCORRECTLY ALTER DATA FOR A DIFFERENT INSTALLATION INSTANCE IF YOU USE THE WIZARD'S BACK BUTTON

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • This issue is triggered by a very specific set of conditions.
    All of these conditions must be true in order to trigger this
    problem:
    
    - The affected system has multiple instances of WebSphere
    Application Server products installed.
    - One of the WebSphere Application Server instances was updated
    with a fix pack which failed to install properly.
    - Later, that same WebSphere Application Server instance was
    updated by the UpdateInstaller using its "Failure Recovery"
    feature, and the failed fix pack was uninstalled.
    
    After following a specific sequence of events (described below),
    the UpdateInstaller will incorrectly update a WebSphere
    Application Server product instance with data that is supposed
    to be applied to a different product instance.  When this
    occurs, both product instances are irreversibly damaged.  The
    products must be re-installed or restored from a system backup.
    
    ----------------------------------------------------------------
    
    The effects of this defect are not immediately obvious.
    The problem only becomes apparent when using the UpdateInstaller
    to install or uninstall fixes from the WebSphere Application
    Server product.
    
    One product will show that a fix pack is present which should
    not be present, because the UpdateInstaller claimed to have
    uninstalled it earlier.  The product's version information (such
    as that information obtained using the versionInfo utility) will
    show a version that indicates that the fix pack is not present,
    but the UpdateInstaller will indicate that the fix pack is
    present and can be uninstalled.  Attempting to uninstall the fix
    pack will produce an error.  The updatelog.txt for the attempt
    will indicate that the fix pack could not be uninstalled because
    the backup file(s) for that fix pack are missing.
    
    The other product may potentially show that a fix pack has been
    removed which is still present.  The product's version
    information indicates a version that implies the fix pack is
    installed.  However, it is impossible to remove the fix pack
    because the UpdateInstaller indicates it is not present.  In
    addition, attempting to install the same fix pack will fail.
    The updatelog.txt file will indicate that a "duplicate entry"
    error occurred while attempting to create a backup of the fix
    pack data.
    
    (Please note that "duplicate entry" errors can occur for a
    variety of reasons.  If you encounter a "duplicate error" error
    while installing a fix pack and the symtoms do not match the
    conditions outlined above, then there may be another reason for
    the issue.)
    
    ----------------------------------------------------------------
    
    Here is more specific information about how the event is
    triggered.  This information is provided so that system
    administrators and service personnel can retrace recent events
    to see if a system was affected by this problem.
    
    1. One WebSphere Application Server product install (for
    example, called "wasA") is partially updated with a Fix Pack,
    but the Fix Pack installation failed.
    
    2. At a later time, the UpdateInstaller wizard is started.
    The UpdateInstaller wizard asks the user for the location of the
    product to be modified.  The user chooses a different WebSphere
    Application Server product installation than in step 1.  (For
    example, called "wasB".)
    
    3. The user selects the option to "install" a Fix Pack on wasB.
    However, instead of proceeding to select and install Fix Packs,
    the user uses the "Back" button.
    
    4. The user navigates backwards to the panel where the
    UpdateInstaller asks the user for the location of the product to
    be modified.  The user changes the selection to "wasA", which
    has the partial (failed) fix pack installation.
    
    5. Upon selecting "wasA", the UpdateInstaller informs the user
    that "wasA" has a failed fix pack.  After selecting "Next", the
    UpdateInstaller automatically removes the failed Fix Pack from
    "wasA".  After claiming to have successfully removed the Fix
    Pack, the user can choose to exit the UpdateInstaller.
    
    The issue that is the focus of this APAR occurs in step 5.
    Although the UpdateInstaller has successfully removed a fix pack
    from "wasA", the UpdateInstaller will erroneously write some
    data to "wasB" that indicates the fix pack was removed.  If
    "wasB" previously had that same fix pack installed, then "wasB"
    becomes damaged.  In addition, "wasA" is not updated with vital
    data to indicate that the fix pack was removed, which means
    "wasA" is also damaged.
    

Local fix

  • In order to avoid this issue, avoid using the "Back" button in
    the UpdateInstaller wizard in UpdateInstaller V7.0.0.11 and
    earlier.  If you make an accidental selection, quit the
    UpdateInstaller and restart it.
    
    ----------------------------------------------------------------
    
    If two WebSphere Application Server products on a system are
    damaged by this defect, then unfortunately they cannot be safely
    recovered.  It is necessary to reinstall both affected products
    in order to ensure their fix data is reliable.
    
    As an alternative to reinstalling the products, recover the
    affected WebSphere Application Server products from a system
    backup.  If a system backup is available, please note the
    following:
    
    - When recovering a copy of WebSphere Application Server from a
    system backup, be sure to wipe out the existing (old, corrupted)
    product directly entirely before restoring the entire product
    directory from backup.  Do not extract backup data on top of the
    existing product directory.
    
    - When recovering the product from a system backup, please be
    sure to also recover a copy of the ".nifregistry" file.  The
    .nifregistry file location varies depending on the operating
    system and whether the product was installed as root or
    non-root.  Refer to the MustGather for UpdateInstaller issues
    for details. (technote 1255972)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Update Installer (UPDI) may             *
    *                      incorrectly alter data for a            *
    *                      different installation instance if      *
    *                      you use the wizard's "Back" button      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When you use the "Back" button to choose two different
    WebSphere Application Server locations, UPDI may mix the meta
    information of the two installation instance. When the
    you install or uninstall maintenance, UPDI may modify the
    data incorrectly.
    

Problem conclusion

  • When you use the "Back" button to re-locate a WebSphere
    Application Server installation instance, Update Installer
    (UPDI) will now clear all the information from the previous
    WebSphere Application Server installation instance selected
    and re-construct the information for the new WebSphere
    Application Server installation instance.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM18760

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-20

  • Closed date

    2010-08-27

  • Last modified date

    2010-08-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM18760

Modified date: 27 August 2010