Troubleshoot migration

 

+

Search Tips   |   Advanced Search

 

Overview

• The following problems can occur when using the pre-upgrade tool:

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

     install_dir\bin

     ...and launch either file from that location.

  2. The DB2 JDBC driver and DB2 JDBC driver (XA) cannot be found in the drop down list of supported JDBC providers in the administrative console The administrative console no longer displays 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.

  3. You receive message...

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

     Several possible reasons for this error exist:

     • If WAS V4.0.x or 5.x is installed, you might not have run the WASPreUpgrade tool from the bin directory of the V6 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 WAS Release 4.0 migration utility, not the v6 migration utility.

       2. Alter your environment path or change the current directory so that we can launch the WAS V6 WASPreUpgrade program.

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

  4. MIGR0125E: The call to XMLConfig was not successful error when trying to run WASPreUpgrade

     The WASPreUpgrade tool saves selected files from WAS VV4.x and V5.x bin directories. It also exports the existing application server configuration from the repository.

     If you are migrating from WAS V4.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.

• The following problems can occur when using the post-upgrade tool:

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

  2. You receive message: MIGR0102E: Invalid Command Line. MIGR0105E: You must specify the primary node name. The most likely cause of this error is that V4.0.x or 5.x of the WAS is installed, and the WASPostUpgrade tool was not run from the bin directory of the WAS V6 installation root.

     If the following messages appear when the WASPostUpgrade tool is run, the V4.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>]]}"