You might encounter problems while migrating from an older version of WebSphere Application Server.
profileName: profileName cannot be empty profilePath: Insufficient disk space
These error messages might be displayed if you enter a profile name that contains an invalid character such as a space. Rerun the Migration wizard, and verify that there are no invalid characters in the profile name such as a space, quotes, or any other special characters.
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.
This command results in a display of all objects in WebSphere Application Server's namespace, including the directory path and object name.
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 also has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
This problem can occur if you are trying to run the WASPreUpgrade tool from a directory other than the WebSphere Application Server Version 6.1 app_server_root\bin. Verify that the WASPreUpgrade script resides in the Version 6.1 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 5.0 migration utility, not the Version 6.1 migration utility.
This problem can occur if you are trying to run the WASPostUpgrade tool from a directory other than the WebSphere Application Server Version 6.1 app_server_root\bin. Verify that the WASPostUpgrade script resides in the Version 6.1 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 5.x or 6.0.x is installed and the WASPostUpgrade tool was not run from the bin directory of the Version 6.1 installation root.
To correct this problem, run the WASPostUpgrade command from the bin directory of the WebSphere Application Server Version 6.1 installation root.
MIGR0304I: The previous WebSphere environment is being restored. com.ibm.websphere.management.exception.RepositoryException: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invoke MIGR0286E: The migration failed to complete.
profile_root/properties
com.ibm.SOAP.requestTimeout=1800
backupDirectory/profiles/profile_name/properties
wsadmin -f application_script -conntype NONE
MIGR0304I: The previous WebSphere environment is being restored. java.lang.Exception: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Class 'WASQueueConnectionFactory' not found. (file:app_server_root/config/cells/cell_name/nodes/node_name/resources.xml, 7, 221) MIGR0286E: The migration failed to complete.
An incomplete or unsuccessful installation of internal messaging on the target node might cause the migration to fail in this way. If your resources.xml file is corrupted by a failed internal-messaging installation, for example, the file might not include the namespace information that the WebSphere Common Configuration Model (WCCM) needs during WASPostUpgrade command processing.
xmlns:xmi="http://www.omg.org/XMI" xmlns:resources.jms="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.jms.xmi" xmlns:resources.j2c="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.j2c.xmi" xmlns:resources="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.xmi" xmlns:resources.jms.internalmessaging="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.jms.internalmessaging.xmi" xmlns:resources.mail="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.mail.xmi" xmlns:resources.url="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.url.xmi"
xmlns:xmi="http://www.omg.org/XMI" xmlns:resources.jms="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.jms.xmi" xmlns:resources.j2c="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.j2c.xmi" xmlns:resources="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.xmi" xmlns:resources.jms.internalmessaging="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.jms.internalmessaging.xmi" xmlns:resources.mail="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.mail.xmi" xmlns:resources.url="http://www.ibm.com/websphere/appserver/schemas/5.0/resources.url.xmi"
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 5.0 migration utility, not the Version 6.1 migration utility.
MIGR0253E: The backup directory migration_backup_directory does not exist.
For example, the directory might have been a subdirectory of the Version 5.x or 6.0.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.
During the course of a deployment manager or a managed node migration, WASPostUpgrade might disable the old environment. If after running WASPostUpgrade you want to run WASPreUpgrade again against the old installation, you must run the migrationDisablementReversal.jacl script located in the old app_server_root/bin directory. After running this JACL script, your Version 5.x or 6.0.x environment will be in a valid state again, allowing you to run WASPreUpgrade to produce valid results.
/websphere61/appserver/profiles/dm_profile/temp/nodeX_migration_temp
The logs and everything else involved in the migration for this node on the deployment manager node are located in this folder. This folder will also be required for IBM support related to this scenario.
If any of the Version 6.1 applications fail to install during a federated migration, they will be lost during the synchronizing of the configurations. The reason that this happens is that one of the final steps of WASPostUpgrade is to run a syncNode command. This has the result of downloading the configuration on the deployment manager node and overwriting the configuration on the federated node. If the applications fail to install, they will not be in the configuration located on the deployment manager node. To resolve this issue, manually install the applications after migration. If they are standard Version 6.1 applications, they will be located in the app_server_root/installableApps directory.
To manually install an application that was lost 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
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
MIGR0327E: A failure occurred with stopNode. MIGR0272E: The migration function cannot complete the command.
WebSphere Application Server Version 6.0.2 uses a Java virtual machine (JVM) in 32-bit mode. The Migration wizard for WebSphere Application Server Version 6.1.x calls the WASPostUpgrade.sh script, which attempts to run the JVM for Version 6.0.2 in the 64-bit mode when the server stops the Version 6.0.2 node.
cd /opt/IBM/WebSphere/AppServer/bin
. "$binDir" /setupCmdLine.sh
JVM_EXTRA_CMD_ARGS=""
app_server_root/bin/manageprofiles.sh -delete -profileName profile_name
The applications that exist in the Version 5.x or Version 6.0.x configuration might have incorrect deployment information—usually, 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 6.1 configuration using the administrative console or an install script.
Exception = java.lang.ClassNotFoundException Source = com.ibm.ws.cluster.selection.SelectionAdvisor.<init> probeid = 133 Stack Dump = java.lang.ClassNotFoundException: rule.local.server at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code)) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:106) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at com.ibm.ws.cluster.selection.rule.RuleEtiquette.runRules(RuleEtiquette.java:154) at com.ibm.ws.cluster.selection.SelectionAdvisor.handleNotification(SelectionAdvisor.java:153) at com.ibm.websphere.cluster.topography.DescriptionFactory$Notifier.run(DescriptionFactory.java:257) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1462)
Exception = java.io.IOException Source = com.ibm.ws.cluster.topography.DescriptionManagerA. update probeid = 362 Stack Dump = java.io.IOException at com.ibm.ws.cluster.topography.ClusterDescriptionImpl.importFromStream(ClusterDescriptionImpl.java:916) at com.ibm.ws.cluster.topography.DescriptionManagerA.update(DescriptionManagerA.java:360) Caused by: java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java(Compiled Code)) at java.io.DataInputStream.readUTF(DataInputStream.java(Compiled Code)) at com.ibm.ws.cluster.topography.KeyRepositoryImpl.importFromStream(KeyRepositoryImpl.java:193)
During migration, Version 6.1 cluster information is distributed throughout the cell. Version 6.0.x nodes that are not at Version 6.0.2.11 or later fail to read this information.
To avoid this problem, upgrade all Version 6.0.x nodes that will be contained in or interoperating with a Version 6.1 cell to Version 6.0.2.11 or later before migrating your deployment managers to Version 6.1.
[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)
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/61AppServer/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:
This indicates that a configuration error was detected before beginning the migration process. This can be due to either incorrect data entered when you created the migration jobs or a configuration problem. Review the log output for the error detected, then correct and rerun. The logs are located in temporary_directory_location/nnnnn, where temporary_directory_location is the value that you specified when you created the migration jobs (where the default is /tmp/migrate) and nnnnn is a unique number that is generated and displayed during the creation of your migration jobs as well as displayed in the JESOUT DDNAME of the WROUT and WRERR steps of your batch job stream.
In the event of failure in the migration job after the Verify step, you can rerun the migration job; but first, you must delete the WebSphere Application Server for z/OS configuration home directory created in the CRHOME step. This corresponds to the home directory that you entered when you created the migration jobs, and it can also be found in the migration JCL environment variable V6_HomeDir. Because the migration procedure creates a new configuration file system for each node being migrated, it is a simple process to delete the configuration and start from scratch.
A federated node is the most complex node to migrate because it is essentially two migrations rolled into one. A federated node requires a migration of the node configuration information contained in the deployment manager's master repository as well as the configuration information contained in the federated node. Federated node migration requires an active connection to the deployment manager. If you have security enabled, it is essential that you follow the instructions that were generated when you created the migration jobs. The migration job must be submitted with a WebSphere Administrator's user ID that has been properly configured for obtaining secure connections.
If you select the option for the migration process to install the enterprise applications that exist in the Version 5.x or Version 6.0.x configuration into the new Version 6.1 configuration, you might encounter error messages during the application-installation phase of migration.
The applications that exist in the Version 5.x or Version 6.0.x configuration might have incorrect deployment information—usually, 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.
Do this by adding the RESTART=FINISHUP parameter to the job card and resubmitting the job.
The migration logs are located in temporary_directory_location/nnnnn, where temporary_directory_location is the value that you specified when you created the migration jobs (where the default is /tmp/migrate) and nnnnn is a unique number that was generated during the creation of your migration jobs. Normally, the space requirements for the migration logs are small. If you enable tracing, however, the log files can be quite large. The best practice is to enable tracing only after problems have been found. If tracing is required, try to only enable tracing related to the step in the process that is being debugged. This will help to reduce the space requirements.
TraceState=enabled profileTrace=disabled preUpGradeTrace=disabled postUpGradeTrace=enabled
During migration, a backup copy of your Version 5.x or 6.0.x configuration is made. This backup becomes the source of the information being migrated. The default backup location is /tmp/migrate/nnnnn. This location can be changed when you create the migration jobs. Depending on the size of the node being migrated, this backup can be quite large. If your temporary space is inadequate, then you will need to relocate this backup.
Each z/OS installation is different with respect to job classes and time limitations. Make sure you have specified appropriate job classes and timeout values on your job card.
MIGR0339I: Application WISO_wisoadmin_war.ear is deploying using the wsadmin command. MIGR0241I: Output of wsadmin. Error: unable to allocate 268435456 bytes for GC in j9vmem_reserve_memory. JVMJ9VM015W Initialization error for library j9gc23(2): Failed to instantiate heap. 256M requested Could not create the Java virtual machine.
The problem is that the WASPostUpgrade script launched from bbomigrt2.sh does not have enough remaining address space to initialize the Java virtual machine (JVM). Typically, this indicates that the spawned process is running in the same address space as the WASPostUpgrade JVM.
You can use the environment variable _BPX_SHAREAS to tell the underlying process whether or not spawned processes should share the same address space as the parent process. The default value (null) is NO, but administrators can change this to YES or MUST to get a performance benefit because the address space does not need to be copied during fork or spawn actions.
export _BPX_SHAREAS = NO
After the migration job completes, you can update the profile to reset _BPX_SHAREAS to its original value.
Review the instructions that were generated when you created the migration jobs. Verify that the JCL procedures have been copied over correctly to your PROCLIB, the RACF definitions have been created, the Version 6.1 libraries have been authorized, and, if required, your STEPLIB statements to the Version 6.1 libraries have been specified. Make sure that the daemon process associated with your cell is at the appropriate level. The daemon process must be at the highest WebSphere Application Server for z/OS version level of all servers that it manages within the cell.
Exception = java.lang.ClassNotFoundException Source = com.ibm.ws.cluster.selection.SelectionAdvisor.<init> probeid = 133 Stack Dump = java.lang.ClassNotFoundException: rule.local.server at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code)) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:106) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at com.ibm.ws.cluster.selection.rule.RuleEtiquette.runRules(RuleEtiquette.java:154) at com.ibm.ws.cluster.selection.SelectionAdvisor.handleNotification(SelectionAdvisor.java:153) at com.ibm.websphere.cluster.topography.DescriptionFactory$Notifier.run(DescriptionFactory.java:257) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1462)
Exception = java.io.IOException Source = com.ibm.ws.cluster.topography.DescriptionManagerA. update probeid = 362 Stack Dump = java.io.IOException at com.ibm.ws.cluster.topography.ClusterDescriptionImpl.importFromStream(ClusterDescriptionImpl.java:916) at com.ibm.ws.cluster.topography.DescriptionManagerA.update(DescriptionManagerA.java:360) Caused by: java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java(Compiled Code)) at java.io.DataInputStream.readUTF(DataInputStream.java(Compiled Code)) at com.ibm.ws.cluster.topography.KeyRepositoryImpl.importFromStream(KeyRepositoryImpl.java:193)
During migration, Version 6.1 cluster information is distributed throughout the cell. Version 6.0.x nodes that are not at Version 6.0.2.11 or later fail to read this information. To avoid this problem, upgrade all Version 6.0.x nodes that will be contained in or interoperating with a Version 6.1 cell to Version 6.0.2.11 or later before migrating your deployment managers to Version 6.1.
After migration, carefully review the job output and log files for errors.
If you migrate a node to Version 6.1 then discover that you need to revert back to Version 5.x or 6.0.x, see Rolling back your environment.
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 also has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
If you did not find your problem listed, contact IBM support.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |