PH45605: WASPREMIGRATION FAILS WHEN THE PROFILES ARE IN THE $WAS_HOME DIRECTORY

APAR status

• Closed as program error.

Error description

• At the beginning of WASPreUpgrade, it builds a list of files to
  process and eventually copy over into the backup directory. As
  an optimization, if --oldProfile is specified, migration removes
  all other files in the profile's parent directory from the list
  of files to process, making an assumption that these files are
  either other profiles (correct if the profile is in the default
  profiles directory) or completely irrelevant files to the
  migration (correct if the profile is entirely outside of the WAS
  directory tree).
  
  
  However, the client found a scenario where WASPreUpgrade is
  wrong to make that assumption: if the profile is located with in
  the WAS directory tree alongside other files that WASPreUpgrade
  should be migrating. In this case, WASPreUpgrade was removing
  all install-level files/directories from the list of files to
  process, assuming they were other profiles. This explains why
  websphere_backup was never created (no actual install-level file
  was processed and copied) and why there was no error in the
  trace (because it never knew those files should be moved over).
  

Local fix

• There's also a possible workaround: if --oldProfile is not
  specified, WASPreUpgrade will collect all profiles in the
  install, and will therefore skip the optimization that led to
  removing the install-level files from the list. Then you can use
  --oldProfile on WASPostUpgrade to specify which profile to
  migrate from. You'll still have to take a backup of all profiles
  at least twice, once before migrating the Dmgr and once after
  migrating the Dmgr and syncing all nodes to the new Dmgr, but it
  should let you by if you need to get the migration done before
  we can get a test fix out.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server version to version migration tools   *
  ****************************************************************
  * PROBLEM DESCRIPTION: WASPreUpgrade fails because             *
  *                      wasprofile.properties could  not be     *
  *                      opened from backup directory            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This issue occurs when -oldProfile is specified and the
  profile is located directly in $WAS_HOME, rather than in
  $WAS_HOME/profiles or outside the WAS directory structure
  altogether.
  The WASPreUpgrade process will get most of the way
  through copying all files to the backup directory, but will
  fail when it tries to open wasprofile.properties from the
  backup directory. Additionally, the backup directory will not
  have a websphere_backup directory within it after
  WASPreUpgrade fails.
  This is caused by a performance optimization that assumed that
  if -oldProfile is specified, the parent of the specified
  profile's directory does not contain any files outside the
  profile directory that need to be migrated. However, when that
  parent is $WAS_HOME, it causes migration to skip collecting
  all install-level files it needs to, including
  wasprofile.properties.
  

Problem conclusion

• WASPreUpgrade was adjusted to not ignore install-level files
  when the profile being migrated is in $WAS_HOME.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.13. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

• Run WASPreUpgrade without the -oldProfile parameter. All profile
  
  in the install will be collected, and the error will be avoided.
  

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