IBM Support

PI98695: DMGR CANNOT GET STATUS OF NODE AFTER MIGRATING DMGR WITH CLONE TRUE AND MIGRATING FEDERATED NODE WITH CLONE FALSE

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 migrating the Dmgr with the -clone true option, the
    migration tooling does not enforce the same option for
    Federated Nodes in the cell.
    
    If you do not specify the -clone option or set it to false, the
    migration will still continue and succeed.
    
    However, certain config files are not migrated properly
    resulting in the Dmgr not being able to communicate properly
    with the node agent.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WASPostUpgrade Clone Migration for   *
    *                  Federated Node.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Clone process allows a Federated    *
    *                      Node to be migrated with Clone false    *
    *                      even though its Deployment Manager      *
    *                      was migrated with Clone true.  This     *
    *                      causes some inconsistensies in the      *
    *                      the Federated Node's configuration      *
    *                      after migration completes.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The code ensures that the Federated node cannot be cloned if
    the Deployment Manager was not cloned.  But it was not looking
    at the opposite condition.  Although the migration completed
    without any errors, there were some configuration
    inconsistencies which WSAPostUpgrade did not correct.
    

Problem conclusion

  • Fix the code to check to be sure that the Clone option used by
    the Deployment Manager migration matches what is used by the
    Federated Node migration.
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.10.  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

    PI98695

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-01

  • Closed date

    2018-10-15

  • Last modified date

    2018-10-15

  • 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: 900

Reference #: PI98695

Modified date: 15 October 2018


Translate this page: