PI30817: MIGRATION CHANGES CORE GROUP IDS TO THE DEFAULT CORE GROUP ID

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The migration process changes the coregroup ID to the default
  core group ID.
  
  This causes issue when attempting to remove coregroups
  

Local fix

• Goto
  $WAS_HOME/profileTemplates/cell/dmgr/documents/config/templates/
  default
  
  copy coregroup-template.xml to coregroup-template.xml.orig
  edit coregroup-template.xml and remove the following from line
  2:
     xmi:id="CoreGroup_1080665362339"
  
  This will cause the template to be read in, later during
  migration our call to the WCCM code will find the xmi:id
  missing and it will assign a  new one.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Migration tools                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Non-default CoreGroup UUIDs are set     *
  *                      to be the same as the default           *
  *                      CoreGroup, causing problems when        *
  *                      trying to remove.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The template file for CoreGroup.xml has the same UUID as does
  the default CoreGroup from the profile template's
  CoreGroup.xml.  Because migration is using the template and
  not a factory to generate the non-default CoreGroup the UUID
  is not generated.
  

Problem conclusion

• Migration tooling will now check to see if the target
  coregroup.xml was read in from a template.  If it is then a
  new UUID will be generated for that new CoreGroup object.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.11 and 8.5.5.6.  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 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

• R800 PSY

     UP

• R850 PSY

     UP