PI89175: WASPREUPGRADE.SH WITH "-MACHINECHANGE TRUE" FAILS WITH ERROR MIGR0104E

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
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
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Client is attempting to do a remove migration from WAS V7 to
  WAS V8.5.5.
  These are the steps that caused the problem:
  1. He ran this command on the WAS V855 installation:
  ./createRemoteMigrJar.sh -targetDir /tmp/preupgrade -skipJava
  2. He copied the jar file to /opt/IBM/WebSphere/migrate on his
  WAS V7 machine and extracted it.
  3. From /opt/IBM/WebSphere/migrate/bin he ran the command:
  ./WASPreUpgrade.sh /tmp/preupgrade
  /opt/IBM/WebSphere/AppServer/ -machineChange true
  4. If fails with error
   "MIGR0104E: You must specify the currently installed
  Application Server directory name."
  5. Running versionInfo.sh shows the information about WAS V7.
   --
  The WASPreUpgrade.sh command thinks it is running from the WAS
  V7 product and not WAS V885.
  The problem was caused by this setting in the
  /opt/IBM/WebSphere/migrate/properties/wasprofile.properties
  file:
  WS_PROFILE_REGISTRY=/opt/IBM/WebSphere/Profiles/properties/
  profileRegistry.xml
  Since this value is valid on the WAS V7 system it causes the
  WAS V7 product to used instead on WAS V885.
  

Local fix

• The client worked around the problem by commenting out
  WS_PROFILE_REGISTRY=/opt/IBM/WebSphere/Profiles/properties/profi
  leRegistry.xml
  in /opt/IBM/WebSphere/migrate/properties/wasprofile.properties
  file.
  
  Keywords: migation migrate migrating waspreupgrade
  waspostupgrade wl3mig
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of the IBM WebSphere Application  *
  *                  Server Remote Migration Tool                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The remote WASPreUpgrade tool is        *
  *                      calling the version of the tool.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When source and target installations are set up with similar
  paths to the profile registry in the wasprofile.properties
  file, the setupCmdLine script gets confused and incorrectly
  sets may WAS variables incorrectly.  Thus is tries to run the
  wrong version of the WASPreUpgrade command.
  

Problem conclusion

• When gathering the necessary data/files for the remote
  migration jar, simply set the location of the profile registry
  value back to its default location in the
  wasprofile.properties file.  The default prepends the location
  with a ${was.install.root} variable.  This causes the
  setupCmdLine to find the WASPreUpgrade command from the
  correct location.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.6 and 8.5.5.13.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Remove the WAS_PROFILE_REGISTRY variable from the
  wasprofile.properties file in the remote migration directory.
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP