PI74928: Files referenced by a profile's XML configurantion are missing under the user install root after migration

9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• During a migration shared libraries, resource files (database
  driver jars), and key/trust files do not get correctly copied
  to the new WebSphere Application Server environment. This can
  happen when the profile name doesn't match the profile's
  directory name and the machineChange flag is set to true
  (remote migration).
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Configuration Migration tools.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: After a migration, files referenced     *
  *                      from the configuration are missing      *
  *                      such as shared libraries, resource      *
  *                      files, and key/trust files.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WASPostUpgrade trace will show
  com.ibm.wsspi.migration.document.exceptions.NotFoundException
  errors and files referenced by configuration xml will be
  missing after a migration. This problem only occurs when the
  WebSphere profile name doesn't match the profile's directory
  name and machineChange is set to true (remote migration).
  

Problem conclusion

• The WASPostUpgrade code has been updated to correctly map the
  profile name and profile directory name during remote
  migrations when linking files from the migration backup
  directory to the new WebSphere profile.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.3.  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

• R900 PSY

     UP