Migration utility troubleshooting tips

If you are encounter problems migrating an application from a previous version of WAS to V5...

• Look for these log files and browse them for clues...

  • $WAS_HOME/logs/WASPostUpgrade.time stamp.log

  • migration_backup_dir/WASPreUpgrade.time stamp.log

  • $WAS_HOME/logs/clientupgrade.time stamp.log

• Look for MIGR0259I: Completed successfully or MIGR0271W... Completed with warnings in the migration_backup_dir/WASPreUpgrade.time stamp.log, migration_backup_dir/WASPreUpgrade.time stamp.log, or $WAS_HOME/logs/clientupgrade.time stamp.log.

  If MIGR0286E... Completed with errors. appears, 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. If the errors persist, rerun the command with trace enabled.

• To generate more detailed messages when running the migration tools, enable tracing...

  • when running the WASPreUpgrade or WASPostUpgrade tools, add the following strings when you invoke them: -traceString "*=all=enabled" -traceFile migration_backup_dir/filename.

  • when running ClientUpgrade, add the following strings to the command line when you invoke it: -traceString "*=all=enabled" -traceFile $WAS_HOME/logs/filename.

• Open the log analyzer on the service log of the server which is hosting the resource you are trying to access and use it to browse error and warning messages.

• With WAS running, run the dumpNameSpace on Windows or dumpNameSpace.sh command on Unix, and pipe, redirect, or "more" the output so that it can be easily viewed. This command results in a display of all objects in WAS's namespace, including the directory path and object name.

• If the object a client needs to access does not appear, use the administrative console to verify that...

  • The server hosting the target resource is started.

  • The web module or EJB container hosting the target resource is running.

  • The JNDI name of the target resource is properly specified.

• To view detailed information on the runtime behavior of WAS's Naming service, enable trace on the following components and review the output...

  • com.ibm.ws.naming.*

  • com.ibm.websphere.naming.*

If none of these steps solves the problem, see Troubleshooting migration problems for tips on specific migration problems. If none of these match your problem, check to see if the problem is identified and documented using the links in Diagnosing and fixing problems: Resources for learning. 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 IBM Support page.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see IBM Support page.

 

See Also

Troubleshooting installation problems

 

---