APAR status
Closed as program error.
Error description
Migration fails when Fed node cloned a second time. Need better explanation.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Migration Tooling * **************************************************************** * PROBLEM DESCRIPTION: Need better message for a Double * * migration of node when cloning. * **************************************************************** * RECOMMENDATION: * **************************************************************** This is a follow up issue for when a customer tries to reset the target Federated profile after it has been successfully migrated. This should not be allowed.
Problem conclusion
Output a better message letting the customer know that the node was successfully cloned migrated previously and cannot be re-migrated. 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
PH21293
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
2020-01-22
Closed date
2020-05-01
Last modified date
2020-05-01
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
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021