Migration troubleshooting tips

If you encounter a problem when you are migrating from a previous version of WebSphere Application Server to Version 6.0.x, check your log files and other available information.

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

  • profile_root/logs/WASPostUpgrade.time stamp.log

  • profile_root/logs/WASPostUpgrade.trace

  • migration_backup_dir/WASPreUpgrade.time stamp.log

  • app_server_root/logs/clientupgrade.time stamp.log

• Look for MIGR0259I: The migration has successfully completed. or MIGR0271W: The migration completed with warnings. in the migration_backup_dir/WASPreUpgrade.time stamp.log, migration_backup_dir/WASPreUpgrade.time stamp.log, or app_server_root/logs/clientupgrade.time stamp.log.

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

• Look at your trace output to see more detailed message information. To locate the trace output:

  • for the

    WASPreUpgrade command, look in the backupDirectory.

  • for all other commands, look in the logs directory of the profile being modified. The names of the log files follow this format:

    commandname.timestamp.trace

    where commandname is

    WASPostUpgrade or another command, and timestamp is a date timestamp.

  If you are still unable to find your trace output, see Tracing and logging configuration . See the following articles for more information:

  • WASPreUpgrade command

  • WASPostUpgrade command

  • The clientUpgrade command

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

• With WebSphere Application Server running, run the

  dumpNameSpace command and pipe, redirect, or "more" the output so that it can be easily viewed. This command results in a display of all objects in WebSphere Application Server'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 enterprise Java bean 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 WebSphere Application Server'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 for tips on specific migration problems. 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 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.

Related tasks

Related reference

Troubleshoot the installation

Searchable topic ID: rtrb_migratncomp