You might encounter problems while migrating from an older version of WebSphere® Application Server.
This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgIf 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.
This produces a very large trace file; for example, it can exceed 1 GB for the WASPostUpgrade command.
This is the default.
If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.
If you specify this parameter, you must also specify the -traceFile parameter.
If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.
If you specify the -traceString parameter but do not specify the -traceFile parameter, the script does not generate a trace file.
See the "Tracing and logging configuration" article for information on configuring your tracing and logging settings to help diagnose problems.
For current information available from IBM® Support on known problems and their resolution, read 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, read the IBM Support page.
This problem can occur if you are trying to run the WASPreUpgrade tool from a directory other than the Version 8.0 app_server_root\bin. Verify that the WASPreUpgrade script resides in the Version 8.0 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 6.x migration utility, not the Version 8.0 migration utility.
MIGR0201I: The migration function initialized log file WASPreUpgrade.log. MIGR0300I: The migration function is starting to save the existing Application Server environment. MIGR0302I: The existing files are being saved. MIGR0303I: The existing Application Server environment is saved. MIGR0420I: The first step of migration completed successfully.You might also see a message similar to the following example in the migration trace file:
[10/9/08 18:26:40:363 CDT] 00000000 Save 1 Skipped instance dmgr01 because user root /opt/migration_backup/profiles/dmgr01 does not exist.
The WASPreUpgrade tool writes out a copy of a profileList.ser file that contains pointers to the backup directory to be used by the WASPostUpgrade tool. If that file is not subsequently deleted by migration for any reason, the old paths are used instead of the real paths when you run the WASPreUpgrade tool in later migrations. To resolve this issue, you can safely delete the profileList.ser file and rerun the WASPreUpgrade tool.
For more information, read WASPreUpgrade command.
[07/16/2011 11:07:10:357 CDT] MIGR0344I: Processing configuration file /opt/WAS61fep/profiles/v6109node74_01/config/cells/ndcell/clusters/Station1EJBCluster /resources.xml. [07/16/2011 11:07:10:436 CDT] org.eclipse.emf.ecore.resource.Resource$IOWrappedExcept ion: Unresolved reference 'DataSource_1310769433958'. (file:/opt/WAS61fep/profiles/v6109node74_01/config/cells/ndcell/clusters/Station1EJBC luster/resources.xml, 9, 323) java.lang.Exception: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Unresolved reference 'DataSource_1310769433958'. (file:/opt/WAS61fep/profiles/v6109node74_01/config/cells/ndcell/clusters/Station1EJBC luster/resources.xml, 9, 323) at com.ibm.wsspi.migration.document.wccm.WCCMDocument.setInputStream(WCCMDocument.ja va:162)You might encounter this problem on a WebSphere Version 6.x node when a DB2 database using IBM JCC Provider Driver has been created, and the WebSphere Version 6.x node is synchronized to the Version 8.0 deployment manager. The Version 6.x node does not support the Version 7.x or Version 8.0 driver level. The node synchronization process is failing to remove all of the driver definitions.
To resolve this problem, backup any resources.xml files that are to be modified. Stop the Version 6.x node agent process. Edit the WebSphere Version 6.x node resources.xml files and remove the orphaned resources.jdbc:CMPConnectorFactory entries prior to running the WASPreUpgrade command. Do not edit the deployment manager copy.
gotchaMIGR0484E: No profiles or instances found with name -profileName wasio2651. MIGR0272E: The migration function cannot complete the command.
The old and new profile names must match. Rerun the WASPostUpgrade command with a Version 8.0 profile that matches the name given as the value following -profileName in the MIGR0484E message.
This problem can occur if you are trying to run the WASPostUpgrade tool from a directory other than the Version 8.0 app_server_root\bin. Verify that the WASPostUpgrade script resides in the Version 8.0 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 6.x is installed and the WASPostUpgrade tool was not run from the bin directory of the Version 8.0 installation root.
To correct this problem, run the WASPostUpgrade command from the bin directory of theVersion 8.0installation 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 6.x migration utility, not the Version 8.0 migration utility.
MIGR0253E: The backup directory migration_backup_directory does not exist.
Read WASPreUpgrade command for more information.
For example, the directory might have been a subdirectory of the Version 6.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
app_server_root/bin/wsadmin -f migration_backup_directory/install_application_name.jacl -conntype NONE
Read WASPostUpgrade command for more information.
When you run the WASPostUpgrade command from the command line:
com.ibm.ejs.ras.TraceNLS*=info
The applications that exist in the Version 6.x configuration might have incorrect deployment information—typically, 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 8.0 configuration using the administrative console or an install script.
ejbModule/com/ibm/websphere/samples/trade/ejb/QuoteHome.java(17): The type Remote is ambiguous
If you did not find your problem listed, contact IBM support.