Troubleshoot migration problems

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.

• Errors using the WASPreUpgrade tool.

• Errors using the WASPostUpgrade tool.

• For other kinds of migration problems, such as an application imported from another version of WebSphere Application Server that will not start, look up the related problem under Troubleshooting by task: What are you trying to do?.

If none of these steps fixes your problem,

• For general tips on migration problems, see Troubleshooting the migration utility.

• Review the Migration topic and its subtopics, which address migrating specific kinds of components.

• Check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes).

• If you do not find your problem listed, contact IBM support.

Errors using the WASPreUpgrade tool

What kind of error are you encountering?

• "Not found" or "no such file or directory" message

• DB2 JDBC driver and DB2 JDBC driver (XA) cannot be found in the drop down list of supported JDBC providers in the administrative console

• MIGR0108E: The specified WebSphere directory does not contain WebSphere version that can be upgraded.

• MIGR0125E: The call to XMLConfig was not successful

Errors using the WASPostUpgrade tool

What kind of error are you encountering?

• "Not found" or "no such file or directory" message

• MIGR0102E: Invalid Command Line. MIGR0105E: You must specify the primary node name.

• MIGR0108E: The specified WebSphere directory does not contain WebSphere version that can be upgraded

• MIGR0116E: The backup directory [migration_backup_directory] does not contain the required xml data file.

• MIGR0253E: The backup directory migration_backup_directory does not exist

"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.

DB2 JDBC driver and DB2 JDBC driver (XA) cannot be found in the drop down list of supported JDBC providers in the administrative console

Starting in WebSphere Application Server, V5.1, the administrative console will no longer display deprecated JDBC provider names. The new JDBC provider names used in the administrative console are more descriptive and less confusing. The new providers will differ only by name from the deprecated ones.

The deprecated names will continue to exist in the jdbc-resource-provider-templates.xml file for migration reasons (for example, for existing JACL scripts). However, you are encouraged to use the new JDBC provider names in your JACL scripts.

MIGR0102E: Invalid Command Line. MIGR0105E: You must specify the primary node name.

The most likely cause of this error is that V4.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 V5 installation root.

If the following messages appear when the WASPostUpgrade tool is run, the Version 4.0 migration tool was run:

• IBM WebSphere Application Server, Release 4.0

• 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:

• If WebSphere Application Server version 4.0.x is installed, you might not have run the WASPreUpgrade tool from the bin directory of the V5 installation root.

  1. Look for the following message to display when the WASPreUpgrade tool runs: IBM WebSphere Application Server, Release 4.0. This message indicates that you are running the WebSphere Application Server Release 4.0 migration utility, not the version 5 migration utility.

  2. Alter your environment path or change the current directory so that you can launch the WebSphere Application Server V5 WASPreUpgrade program.

• WebSphere Application Server version 5 might be installed in the same root directory as the earlier version.

  1. Browse the directory structure of the older version to see whether it contains new V5.0 directories, such as WebSphere\AppServer\logs\ffdc.

  2. Uninstall all versions of WebSphere Application Server.

  3. Reinstall and reconfigure the older version.

  4. Install WebSphere Application Server V5 in a different root directory than the previous one.

• An invalid directory might have been specified when launching the WASPostUpgrade tool, or the WASPreUpgrade tool has not been run.

MIGR0116E: The backup directory [migration_backup_directory] does not contain the required xml data file. error returned from the WASPostUpgrade tool.

If V4.0.x of WebSphere Application Server is installed, you might not have run the WASPostUpgrade tool from the bin directory of the V5.0 installation root.

• If the message IBM WebSphere Application Server, Release 4.0 displays when launching the WASPostUpgrade program, then the wrong version of the program is executing.

• Run the WASPostUpgrade command from the bin directory of the V5.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 V3.5.x and V4.x bin directories. It also exports the existing appserver configuration from the repository.

If you are migrating from WebSphere Application Server V4.0.x Advanced Edition, the WASPreUpgrade command calls the XMLConfig command to export the existing appserver 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:

• The WASPreUpgrade tool was not run prior to the WASPostUpgrade tool.

  1. Check to see if the backup directory specified in the error message exists.

  2. If not, run the WASPreUpgrade .bat or .sh file.

  3. Retry the WASPostUpgrade tool.

• 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.

  1. Determine if the full directory structure specified in the error message exists.

  2. If possible, rerun the WASPreUpgrade tool, specifying the correct full migration backup directory.

  3. If the backup directory does not exist, and the older version it came from is gone, rebuild the older version from a backup repository or XML configuration file.

  4. Rerun the WASPreUpgrade tool.

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.

---

Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?
    

 

---