IBM Support

PH17993: RAR FILES MISSING IF APP SERVER NODE IS CLONE MIGRATED TWICE

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

  • With a clone migration, if a node is migrated twice, ie
    - Migrate DMGR node
    - Migrate App Server node
    - fall back to old level of App Server node
    - Migrate App Server node again
    
    An App Server node shouldn't be allowed to migrate twice -
    since files in the DMGR node get updated when the App Server
    node migrate is done.  This APAR will stop the 2nd migrate
    attempt from working.
    
    Messages seen in the App Server joblog, if RAR file is missing
    after the migration:
    
    J2CA0043E: An Exception occurred while trying to instantiate a
    ResourceAdapter JavaBean instance for the
    installedResourceAdapter defined by key
    cells/cell1/nodes/node1/resources.xml#J2CResourceAdapter_1568668
    327336. The exception is:
    java.lang.ClassNotFoundException:
    com.ibm.ws390.ola.ResourceAdapterImpl
    

Local fix

  • if App Server node needs to fall back, redo the DMGR and App
    Server clone migration
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 Migration Tooling               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Migration allows a federated node to    *
    *                      be migrated twice although not          *
    *                      completely reset.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After a federated node is successfully migrated, the migrated
    files are uploaded to the new Dmgr.  Now if the target node is
    reset, but the Dmgr's config data for that node is not reset,
    a second migration gets totally confused from the config data
    downloaded from the new Dmgr to the backup dir.
    

Problem conclusion

  • Once a node is migrated and the Dmgr has been updated, the
    migration code should not allow the federated node to be reset
    and migrated a second time.  WASPostUpgrade will fail with the
    appropriate message.
    
    The fix for this APAR is targeted for inclusion in fix pack
    v9.0.5.3.  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

    PH17993

  • 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

    2019-10-11

  • Closed date

    2020-02-03

  • Last modified date

    2020-02-03

  • 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 February 2020