IBM Support

PH22671: INCORRECT SERVER UNIQUEID IN CLUSTER.XML AFTER CLONE MIGRATION

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

  • After a clone migration, the cluster.xml files in the cloned
    cell will still have the old cell's server uniqueId's. This
    will cause the generated plugin-cfg.xml file to in turn have
    incorrect cloneID's in it.
    

Local fix

  • Manually update the uniqueId field in the cluster.xml member
    element so that it matches the uniqueId field in the server.xml
    for each server in the cluster.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 Clone Migration on z/OS         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect server uniqueId in cluster    *
    *                      after z/OS clone migration              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When doing a clone migration on z/OS a new uniqueId was
    generated for the servers in their server configuration, but
    the uniqueId for the servers in the cluster configuration was
    migrated from the old environment. This results in the
    plugin creating the wrong value for the JSESSIONID.
    

Problem conclusion

  • When using clone migration on z/OS, the migration code is
    updated to create a new uniqueId for cluster members in the
    cluster configuration and set the corresponding uniqueId for
    the cluster member servers in their server configuration.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.4.
     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

    PH22671

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-26

  • Closed date

    2020-04-28

  • Last modified date

    2020-04-28

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCWL8S","label":"General"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 April 2020