Review this page for troubleshooting tips if you encounter problems while migrating from an older version of WebSphere® ESB
If you select the option for the migration process to install the enterprise applications that exist in the version 6.0.x or 6.1.x configuration into the new version 6.2 configuration, you might encounter some error messages during the application-installation phase of migration.
The applications that exist in the version 6.0.x or 6.1.x configuration might have incorrect deployment information—usually, incorrect XML documents that were not validated sufficiently in previous WebSphere ESB 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 WBIPostUpgrade and produces an "E:" error message.
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.2 configuration using the administrative console or an install script.
After you migrate a managed node to version 6.2, the application server might not start.
[5/11/06 15:41:23:190 CDT] 0000000a SystemErr R com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:198) [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:139) [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:460) [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServer.main(WsServer.java:59) [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [5/11/06 15:41:23:196 CDT] 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) [5/11/06 15:41:23:197 CDT] 0000000a SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
Never change any WebSphere Application Server variables that are configured as a part of profile creation.
If you modify these values incorrectly in old profile, you might get database connectivity, loading, or other missing class exceptions, such as:
10/25/08 13:22:39:650 GMT+08:00] 0000002e J2CUtilityCla E J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/com.ibm.ws.sib/ewps6101.Messaging-BPC.cwfpcCell01.Bus : com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class "com.ibm.db2.jcc.DB2XADataSource" could not be found.DB2,
If either the WBIPreUpgrade or WBIPostUpgrade command-line utility fail due to Out of Memory problems, you can increase the heap size to a number that takes into consideration the size and scope of the environment being migrated, as well as what the machine will allow.
For instructions on how to increase the heap size, use the procedure described in Solution 4 of the following technote: Handling certain Out of Memory conditions when migrating an earlier version of WebSphere Application Server to V6.0.2, V6.1, or 7.0.
While you are using the version 6.2 migration wizard to create a profile when migrating a configuration, you might see the following profile-creation error messages.
profileName: profileName cannot be empty profilePath: Insufficient disk space
These error messages might be displayed if you enter a profile name that contains an incorrect character such as a space. Rerun the migration wizard, and verify that there are no incorrect characters in the profile name such as a space, quotes, or any other special characters.
When you use the migration wizard to migrate a profile from WebSphere ESB version 6.0.x or 6.1.x to version 6.2 on a Solaris x64 processor-based system, the migration might fail during the WBIPostUpgrade step.
MIGR0327E: A failure occurred with stopNode. MIGR0272E: The migration function cannot complete the command.
WebSphere ESB version 6.0.x or 6.1.x uses a Java™ virtual machine (JVM) in 32-bit mode. The migration wizard for WebSphere ESB version 6.2 calls the WBIPostUpgrade.sh script, which attempts to run the JVM for version 6.0.x or 6.1.x in the 64-bit mode when the server stops the version 6.0.x or 6.1.x node.
cd /opt/IBM/WebSphere/ESB/bin
"$binDir" /setupCmdLine.sh
call "%~dp0setupCmdLine.bat" %*
JVM_EXTRA_CMD_ARGS=""
The variable profile_name represents the name of the profile that you want to delete.
If synchronization fails when you migrate a managed node to version 6.2, the server might not start.
ADMU0016I: Synchronizing configuration between node and cell. ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU0005E: Error synchronizing repositories ADMU0211I: Error details may be seen in the file: /opt/WebSphere/62AppServer/profiles/AppSrv02/logs/syncNode.log MIGR0350W: Synchronization with the deployment manager using the SOAP protocol failed. MIGR0307I: The restoration of the previous WebSphere Application Server environment is complete. MIGR0271W: Migration completed successfully, with one or more warnings.These messages indicate the following:
See the syncNode command .
See the GenPluginCfg command .