To resolve problems encountered in migrating an application from an older version of WebSphere Application Server to version 5, determine whether your problems occur using the pre-upgrade tool or the post-upgrade tool.
If none of these steps fixes your problem,
Errors using the WASPreUpgrade tool
What kind of error are you encountering?
Errors using the WASPostUpgrade tool
What kind of error are you encountering?
"Not found" or "no such file or directory" message is returned from the WASPostUpgrade or WASPreUpgrade tool
This problem can occur if you are trying to run the WASPostUpgrade tool or the WASPreUpgrade tool from a directory other than install_dir\bin. Verify that the WASPostUpgrade or WASPreUpgrade .bat or .sh files reside in the install_dir\bin directory, and launch either file from that location.
MIGR0102E: Invalid Command Line. MIGR0105E: You must specify the primary node name.
The most likely cause of this error is that Version 4.0.x of the WebSphere Application Server is installed, and the WASPostUpgrade tool was not run from the bin directory of the WebSphere Application Server Version 5 installation root.
If the following messages appear when the WASPostUpgrade tool is run, the Version 4.0 migration tool was run:
MIGR0002I: java com.ibm.websphere.migration.postupgrade.WASPostUpgrade <backupDirectoryName> -adminNodeName <primary node name> [-nameServiceHost <hostName> [ -nameServicePort <portNumber>]] [-substitute <"key1=value1[;key2=value2;[...]]">] In input xml file, the key(s) should appear as $key$ for substitution.") [-import <xml data file>] [-traceString <trace specification> [-traceFile <filename>]]}"
To correct this problem, run the WASPostUpgrade command from the bin directory of the WebSphere Application Server Version 5 installation root.
MIGR0108E: The specified WebSphere directory does not contain WebSphere version that can be upgraded.
Several possible reasons for this error exist:
MIGR0116E: The backup directory [migration_backup_directory] does not contain the required xml data file. error returned from the WASPostUpgrade tool.
If Version 4.0.x of WebSphere Application Server is installed, you might not have run the WASPostUpgrade tool from the bin directory of the Version 5.0 installation root.
MIGR0125E: The call to XMLConfig was not successful error when trying to run WASPreUpgrade
The WASPreUpgrade tool saves selected files from WebSphere Application Server Version 3.5.x and Version 4.x bin directories. It also exports the existing application server configuration from the repository.If you are migrating from WebSphere Application Server Version 4.0.x Advanced Edition, the WASPreUpgrade command calls the XMLConfig command to export the existing application server configuration from the repository. If errors occur during this part of the WASPreUpgrade command, you might have to apply fixes to the installation to successfully complete the export step. Contact IBM Support for the latest applicable fixes.
MIGR0253E: The backup directory migration_backup_directory does not exist. error returned from the WASPostUpgrade tool
Several possible reasons for this error exist:
An invalid backup directory might be specified. For example, the directory might have been a subdirectory of the V3.5.x or V4.0.x tree, which was deleted after the WASPreUpgrade tool was run and the older version of the product was uninstalled, but before the WASPostUpgrade tool was run.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.