You might encounter problems while migrating from an older version of WebSphere Application Server.
profileName: profileName cannot be empty profilePath: Insufficient disk space
These error messages might be displayed if you enter a profile name that contains an invalid character such as a space. Rerun the Migration wizard, and verify that there are no invalid characters in the profile name such as a space, quotes, or any other special characters.
If MIGR0286E: The migration failed to complete. is displayed, attempt to correct any problems based on the error messages that appear in the log file. After correcting any errors, rerun the command from the bin directory of the product installation root.
This command results in a display of all objects in WebSphere Application Server's namespace, including the directory path and object name.
If you do not see a problem that resembles yours or if the information provided does not solve your problem, contact IBM support for further assistance. For current information available from IBM Support on known problems and their resolution, see the IBM Support page. IBM Support also has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
This problem can occur if you are trying to run the WASPreUpgrade tool from a directory other than the WebSphere Application Server Version 6.1 app_server_root\bin. Verify that the WASPreUpgrade script resides in the Version 6.1 app_server_root\bin directory, and launch the file from that location.
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 existing JACL scripts for example); however, you are encouraged to use the new JDBC provider names in your JACL scripts.
MIGR0108E: The specified WebSphere directory does not contain a WebSphere version that can be upgraded.
This message indicates that you are running the WebSphere Application Server Version 5.0 migration utility, not the Version 6.1 migration utility.
This problem can occur if you are trying to run the WASPostUpgrade tool from a directory other than the WebSphere Application Server Version 6.1 app_server_root\bin. Verify that the WASPostUpgrade script resides in the Version 6.1 app_server_root\bin directory, and launch the 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 WebSphere Application Server Version 5.x or 6.0.x is installed and the WASPostUpgrade tool was not run from the bin directory of the Version 6.1 installation root.
To correct this problem, run the WASPostUpgrade command from the bin directory of the WebSphere Application Server Version 6.1 installation root.
MIGR0304I: The previous WebSphere environment is being restored. com.ibm.websphere.management.exception.DocumentIOException: Unable to copy document to temp file: cells/sunblade1Network/applications/LARGEApp.ear/LARGEApp.ear
Your file system might be full. If your file system is full, clear some space and rerun the WASPostUpgrade command.
MIGR0108E: The specified WebSphere directory does not contain WebSphere version that can be upgraded.
This message indicates that you are running the WebSphere Application Server Release 5.0 migration utility, not the Version 6.1 migration utility.
MIGR0253E: The backup directory migration_backup_directory does not exist.
For example, the directory might have been a subdirectory of the Version 5.x or 6.0.x tree that was deleted after the WASPreUpgrade tool was run and the older version of the product was uninstalled but before the WASPostUpgrade tool was run.
Manually install the applications using the wsadmin command after WASPostUpgrade has completed.
To manually install an application that failed to install during migration, use the wsadmin command to run the install_application_name.jacl script that the migration tools created in the backup directory.
./wsadmin.sh -f migration_backup_directory/install_application_name.jacl -conntype NONE
MIGR0327E: A failure occurred with stopNode. MIGR0272E: The migration function cannot complete the command.
WebSphere Application Server Version 6.0.2 uses a Java virtual machine (JVM) in 32-bit mode. The Migration wizard for WebSphere Application Server Version 6.1.x calls the WASPostUpgrade.sh script, which attempts to run the JVM for Version 6.0.2 in the 64-bit mode when the server stops the Version 6.0.2 node.
cd /opt/IBM/WebSphere/AppServer/bin
. "$binDir" /setupCmdLine.sh
JVM_EXTRA_CMD_ARGS=""
app_server_root/bin/manageprofiles.sh -delete -profileName profile_name
The applications that exist in the Version 5.x or Version 6.0.x configuration might have incorrect deployment information—usually, invalid XML documents that were not validated sufficiently in previous WebSphere Application Server runtimes. The runtime now has an improved application-installation validation process and will fail to install these malformed EAR files. This results in a failure during the application-installation phase of WASPostUpgrade and produces an "E:" error message. This is considered a "fatal" migration error.
In this case, the migration process does not install the failing applications but does complete all of the other migration steps.
Later, you can fix the problems in the applications and then manually install them in the new Version 6.1 configuration using the administrative console or an install script.
If you did not find your problem listed, contact IBM support.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |