PI49976: migration fails when one node name is a substring of another

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an ND cell contains two or more nodes, and one node name
  is a substring of another, one of the nodes configuration
  directory might contain extra files from another node.  This
  can cause migration to fail or to incorrectly configure the
  new WebSphere system.  One possible error that might appear
  would be found at the beginning of the output for the VERIFY
  step of the Migration job BBOWMG3F.  It reads:  Configuration
  Mismatch. You have not specified a Federated WAS Home
  Validaion of Environment Failed. Correct Variables and Re-Try
  Another possible error is that on the newer version of
  WebSphere the migration will have created the wrong short node
  name.
  

Local fix

• Extra files in the config directory can be deleted. If the APAR
  cannot be installed and this needs to be done, contact Support
  for assistance.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM WebSphere Application       *
  *                 Server V7.0                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: migration fails when one node name is   *
  *                      a substring of another.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In a multi-node cell, each node contains a "config" directory
  with configuration files about itself.
  It also contains a directory for the other nodes in the cell.
  For example,
  (profile_name)/config/cell/(cellname)/nodes/(nodename)
  The (nodename) directory for other nodes usually contains only
  two files, serverindex.xml and node-metadata.properties.
  When the problem occurs, these direcotries contain additional
  files.  These additional files are harmless during normal
  operation, can cause migration to fail or assign the wrong
  shortname to the node.
  

Problem conclusion

• A bug existed in the node sync algorithm such that when one
  node name was a substring of another, files could be
  transferred to the wrong node.  The node sync algorithm is
  corrected so the problem no longer occurs.
  
  APAR PI49976 is currently targeted for inclusion in Fix Pack
  7.0.0.41 of WebSphere Application Server.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PI47909

• APAR is sysrouted TO one or more of the following:

Modules/Macros

•    BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UI36529

     UP16/04/09 P F604

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.