Troubleshooting: WebSphere Application Server Migration Issues

Resolving The Problem

Overview:

This topic contains common problems you may encounter when migrating your application server configuration to a newer version/release of WebSphere Application Server.

Some general system problems are:

• OOM
• File Handles
• Disk Space

Other problems may include changes to the previous WebSphere install and/or profile data.

• Check that the userid has proper permissions
• Connectivity
• Network, certificates exchanged, ...
• Check for unexpected symlinks under the WebSphere installation and profile directories
• Hand edited xml and property files with invalid formats can cause problems
• Check for changes to the profile’s setupCmdLine script
• Check the profileRegistry.xml file for valid profiles
• Verify each profile has a valid entry in the properties/fsdb directory

Additional problems can be determined by analyzing the trace log:

• When your migration utility experiences a failure, follow these steps:
Mustgather: Migration Problems

Troubleshooting Migration - The following link is from the V9.0 Knowledge Center and contains common problem/errors you may encounter

https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.migration.nd.doc/ae/tmig_troubleshoot.html

Known Problems and Solutions:

Handling certain Out of Memory conditions when migrating an earlier version of WebSphere Application Server

http://www-01.ibm.com/support/docview.wss?uid=swg21199311

PI70399: MIGRATION TO V9.0 FAILS WHEN INSTALL PATH CONTAINS A SPACE

http://www-01.ibm.com/support/docview.wss?uid=swg1PI70399

Remote migration of node failing with null pointer error.

https://developer.ibm.com/answers/questions/189969/remote-migration-of-node-failing-with-null-pointer.html

createRemoteMigrJar.sh gives the following warning: WSVR0615W: The user.install.root system property is not set.

https://developer.ibm.com/answers/questions/267309/createremotemigrjarsh-gives-the-following-warning/

Helpful Hints

• Migrate only one profile at a time when using the WASPreUpgrade and WASPostUpgrade commands
• Migrate to a clean migration backup directory
• Migrate into a clean target profile. Do not use a profile that has been migrated into before
• Separate the application installs from the WASPostUpgrade migration step by using the “-includeApps” script parameter
• In a complex topology always perform backups of all cell profiles prior to migrating
• After migrating a profile, ensure that the topology is fully functional before moving to the next profile
• Use the migration wizards to help guide you through your migrations