IBM Support

PH15764: WASPOSTUPGRADE FAILS WHEN THE PROFILE WAS CREATED WITH SYM LINKS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Profile was created using a sym-link path causing
    WASPostUpgrade to miss copying files in WAS V8.5.5.
    

Local fix

  • .) shutting down the whole cell incl. dmgr and disabling
    security;
    
    2.) exporting the new root certs from the nodes and importing
    them into the cell default trust store;
    
    3.) starting the cell and do a full resync, then shutting down
    again and activating security, start again;
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Migration Tooling                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Migration Tooling does not handle       *
    *                      profiles created with Sym links.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Migration tooling does not process or collect files which
    are referenced in config files.  These files are either
    ignored or they are collected into a part of the backup
    directory where they do not belong.  This also affects key and
    trust store files.  Which in turn may cause connection
    problems with Fed nodes being migrated.
    

Problem conclusion

  • Given that manageprofiles allows the WAS_INSTALL_ROOT and the
    USER_INSTALL_ROOT variables to be set to a symlink, the
    migration code should take this situation into account as it
    does its processing.  Particularily when collecting files
    referenced in the config files and especially for remote
    migrations.
    
    The fix for this APAR is targeted for inclusion in fix pack
    v9.0.5.3 and v8.5.5.17.  For more information, see 'Recommended
    Updates for WebSphere Application Server':
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH15764

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-16

  • Closed date

    2020-01-20

  • Last modified date

    2020-01-20

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH15764

Modified date: 20 January 2020