MIGR0001I: The class name of the WASPreUpgrade command is WASPreUpgrade
Explanation:
None
User Response:
No user action is required.
MIGR0002I: The class name of the WASPostUpgrade command is WASPostUpgrade
Explanation:
None
User Response:
No user action is required.
MIGR0101W: The migration function cannot create the trace log using file {0}.
Explanation:
The function cannot create the trace file.
User Response:
Verify that the characters of the trace file name are valid for the operating system. The output of the trace is displayed on the console; this output can be captured and sent to IBM service. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0102E: An unsupported command line parameter was used.
Explanation:
The command parameters are incorrectly specified.
User Response:
Verify that all of the parameters are valid and spelled correctly.
MIGR0103E: You must specify the backup directory name.
Explanation:
The backup directory is used to store the configuration information that is migrated to the new release.
User Response:
Run the command again and specify the backup directory.
MIGR0104E: You must specify the currently installed WebSphere Application Server directory name.
Explanation:
You must access the currently installed WebSphere Application Server directory to obtain the configuration information that is migrating to the new release.
User Response:
Run the command again and specify the currently installed WebSphere Application Server directory.
MIGR0105E: You must specify the primary node name.
Explanation:
The primary node name is used to call the XMLConfig command to obtain configuration information for the current release.
User Response:
Run the command and specify the primary node name.
MIGR0106E: The illegal argument {0} is specified.
Explanation:
The specified parameter is not supported by the command.
User Response:
Check the spelling of the parameter and run the command again.
MIGR0107E: An incorrect format for an optional parameter is specified.
Explanation:
Specify optional parameters by entering the name of the parameter, followed by the value of the parameter.
User Response:
Run the command again with the correct format for optional parameters.
MIGR0108E: The directory {0} does not contain a WebSphere version that can be upgraded.
Explanation:
Migration support is provided for WebSphere version 4 and later.
User Response:
If you are migrating to a supported release, verify that the directory name is correct, and rerun the command.
MIGR0110E: The currently installed version of WebSphere Application Server is not supported by this command.
Explanation:
The WASPostUpgrade command is running against an unsupported version of WebSphere Application Server. The WASPostUpgrade command that was invoked might not be using the current version of the WebSphere Application Server directories.
User Response:
Invoke the command in the current WebSphere Application Server directory structure. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0111E: The migration function cannot use the specified backup directory because it is a file.
Explanation:
Specify a directory so that files containing the configuration information for the current release can be saved.
User Response:
Run the command again and specify the name of a directory.
MIGR0112E: The specified backup directory cannot be used because it is not writeable.
Explanation:
Specify a writeable directory so that files containing the configuration information for the current release can be saved.
User Response:
Run the command again and specify the name of a writeable directory.
MIGR0113E: The specified backup directory cannot be used because it cannot be created.
Explanation:
The system is unable to create a directory with the name that you specified.
User Response:
Determine why the directory cannot be created and run the command again. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/, or consult the appropriate operating system documentation.
MIGR0114E: The migration function cannot find the setupCmdLine setting {0}.
Explanation:
The migration function cannot find a specific property in an IBM-supplied file.
User Response:
See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0115E: The migration function cannot run program: {0}.
Explanation:
During migration processing, the function attempted to call another WebSphere Application Server program; the call cannot be successfully completed.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0116E: The backup directory does not contain the required XML data file {0}.
Explanation:
The call to the WASPostUpgrade command was specified without using the -import keyword to specify a particular XML file. If no file is specified, a file named websphere_backup.xml in the backup directory is used.
User Response:
Rerun the WASPostUpgrade command using the -import keyword to specify an XML file that was created using the XMLConfig command on an earlier WebSphere Application Server version.
MIGR0117E: The specified WebSphere Application Server directory does not contain a valid product file {0}.
Explanation:
The specified directory on the migration command does not contain a valid properties/com/ibm/websphere/product.xml file.
User Response:
Rerun the command with a valid WebSphere Application Server XML file name.
MIGR0118E: The WebSphere Application Server directory does not contain a readable product file {0}.
Explanation:
The directory that is specified on the migration command does not contain a readable product.xml file.
User Response:
Rerun the command with a valid WebSphere Application Server directory name.
MIGR0119E: The XML file {0} that was used for import is not valid.
Explanation:
The file that was specified using the -import keyword is not valid.
User Response:
Rerun the command using a valid XML file.
MIGR0120E: The document type definition (DTD) file {0} does not exist.
Explanation:
An internal error occurred. The specified file is expected in the new WebSphere Application Server version bin/migration subdirectory.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0121E: The migration function cannot read the import XML document {0}, exception {1}.
Explanation:
An error occurred while reading the XML file to import during migration.
User Response:
Rerun the command with a valid XML import file. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0122E: The migration function cannot read configuration file {0}.
Explanation:
The function cannot read the specified configuration file.
User Response:
If the file is part of the current WebSphere Application Server configuration, restore the configuration from a previous backup and rerun the command. The WASPostUpgrade command saves backup copies of all the configuration files that it attempts to modify. The backup files are in the same directory structure, with time stamps as part of their names.
MIGR0123E: The migration function cannot import object {0} of type {1}, exception {2}.
Explanation:
During WASPostUpgrade processing, an error occurred while importing the specified object.
User Response:
See the following errors in the migration log for further details. Correct the problem and rerun the command, or use the WebSphere administrative interfaces to complete the configuration of the specified object.
MIGR0124E: The migration function cannot import XML data file {0}.
Explanation:
An attempt to read the specified file failed.
User Response:
Verify that the file exists, and rerun the command.
MIGR0125E: The call to the XMLConfig command was not successful {0}.
Explanation:
The call to the XMLConfig command to obtain the configuration information for the current release failed.
User Response:
Check the log that is created by the command for details, and rerun the command.
MIGR0126E: The call to the XMLConfig command was not successful. Exception {0}.
Explanation:
The call to the XMLConfig command to obtain the configuration information for the current release failed.
User Response:
Check the log that is created by the command for details, and rerun the command.
MIGR0128E: The migration function cannot read the XMLConfig data tag definition file.
Explanation:
The document type definition (DTD) file is expected in the new WebSphere Application Server version bin/migration subdirectory.
User Response:
Check the new bin/migration subdirectory for the DTD file. If the file is missing, try to restore it. Verify that the user ID that is running the migration command has sufficient file system authority. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0201I: The migration function initialized log file {0}.
Explanation:
The specified log file is initialized. A new log file is created for each invocation of the migration commands.
User Response:
No user action is required.
MIGR0202W: The migration function is unable to initialize log file {0}.
Explanation:
The specified log file cannot be initialized. No data is saved in a log file, but output is still routed to the administrative console for you to view.
User Response:
Check the user file permissions before you run the command again.
MIGR0203I: The migration function is working with configuration files from release {0}.
Explanation:
This message logs the WebSphere Application Server version number of the backup configuration.
User Response:
No user action is required.
MIGR0204I: The migration function is calling the XMLConfig program {0}.
Explanation:
The XMLConfig program is being accessed. This program is used to create an XML file that is used to migrate to the new WebSphere Application Server version.
User Response:
No user action is required.
MIGR0205W: The migration function cannot capture the output of {0}.
Explanation:
The function attempted to capture the output while calling another program during migration. The output was not captured, but the migration command still functions normally.
User Response:
Check the migration log file for information about whether the command completed normally. If you are running the WASPreUpgrade function, the file is in the backup directory. If you are running the WASPostUpgrade function, the file is in the new WebSphere Application Server image that is installed in the logs directory. The log name includes a time stamp, so check the log file with the latest creation date.
MIGR0206W: The migration function cannot copy the directory. The source file {0} does not exist.
Explanation:
The function cannot find or copy an expected directory. This missing directory might affect the migration.
User Response:
If this source file must be used to create an enterprise application, use a development environment like WebSphere Studio Application Developer, to add the file to the appropriate location in the enterprise application.
MIGR0207W: The migration function cannot copy the directory {0}.
Explanation:
The function cannot copy the directory. This problem might affect the migration.
User Response:
If the directory must be used to create an enterprise application, use a development environment like WebSphere Studio Application Developer, to add the files from that directory to the appropriate location in the enterprise application.
MIGR0208W: The migration function cannot install the data source {0} into the Java Database Connectivity (JDBC) driver name {1}.
Explanation:
The function cannot add the specified data source to the JDBC driver.
User Response:
After migration is complete, use the system administrative interface to create the data source. The data source must be in the JDBC driver before application servers with data source-dependent deployed applications can start.
MIGR0210I: The migration function is creating a directory {0}.
Explanation:
The directory was created during normal processing.
User Response:
No user action is required.
MIGR0211I: The migration function is copying a directory {0}.
Explanation:
The function is copying a directory and its contents.
User Response:
No user action is required.
MIGR0212E: The migration function cannot create the directory {0}. A file with this name already exists.
Explanation:
An unexpected failure occurred during the creation of a directory.
User Response:
Delete or rename the directory, and rerun the function using either the WASPreUpgrade or the WASPostUpgrade command.
MIGR0213E: The migration function cannot create a directory {0}.
Explanation:
An unexpected failure occurred during the creation of a directory.
User Response:
Verify that the user ID has sufficient file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0214W: The migration function cannot copy the file. Source {0} does not exist.
Explanation:
An unexpected failure occurred when a configuration file was copied.
User Response:
If the source file must be used to create an enterprise application, use a development environment such as the WebSphere Studio Application Developer, to add the file to the appropriate location in the enterprise application.
MIGR0215W: The migration function cannot copy the file and open the destination file {0}.
Explanation:
An unexpected failure occurred while copying a configuration file.
User Response:
Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0216W: The migration function cannot copy the file and transfer from source {0} to destination {1}.
Explanation:
An unexpected failure occurred while copying a configuration file.
User Response:
Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0217W: The migration function cannot close file {0}.
Explanation:
An unexpected failure occurred while closing a configuration file.
User Response:
Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0218I: The migration function is starting to import {0}, action {1}.
Explanation:
The specified object is being imported into the new WebSphere Application Server version. The action value relates to the XMLConfiguration action that is associated with the object in the XML file.
User Response:
No user action is required.
MIGR0219I: The migration function is starting to import {0}.
Explanation:
The specified object is being imported into the new WebSphere Application Server version.
User Response:
No user action is required.
MIGR0220W: The migration function is ignoring object {0} of type {1} because the action was not create, createclone, update, or locate.
Explanation:
The action on the specified object in the input XML file is not supported for migrating objects. Actions that are not supported include delete, export, start, stop, ping, associateclone, or disassociateclone.
User Response:
If you need the object created in the new configuration, then either use a different input XML file, modify the input XML file and rerun migration, or use the WebSphere Application Server administrative interfaces to create the object.
MIGR0221I: The migration function is reading the previously saved configuration file {0}.
Explanation:
The specified configuration file from a previous WebSphere Application Server version is being read. This file is the source for importing objects into the new WebSphere Application Server configuration.
User Response:
No user action is required.
MIGR0222W: The migration function cannot locate an object while importing object {0} of type {1}.
Explanation:
The function cannot locate the specified object in the configuration file in the new WebSphere Application Server configuration. This problem usually occurs for configurations with multiple nodes in the same input XML file, where the specified object is not on the migrating node.
User Response:
Ignore this message if your configuration has multiple nodes in the same input file and the object that is specified is not on the migrating node. Otherwise, verify that the object needs to be added to the configuration, and use the WebSphere Application Server administrative interfaces to create the object.
MIGR0223I: The migration function is adding {0} entry {1} to the model.
Explanation:
The specified object is being added to the configuration of the new WebSphere Application Server version.
User Response:
No user action is required.
MIGR0224W: The migration function is ignoring node entry {0}. This entry is for a different node.
Explanation:
The specified node entry is ignored because it does not match the migrating node. This problem usually occurs for configurations with multiple nodes in the same input XML file, where the specified object is not on the migrating node.
User Response:
Ignore this message if your configuration has multiple nodes in the same input file, and the object that is specified is not on the migrating node. Otherwise, verify that the object needs to be added to the configuration, and use the WebSphere Application Server administrative interfaces to create the object.
MIGR0227W: The migration function cannot make a backup copy of configuration file {0}; exception {1} occurred.
Explanation:
An unexpected failure occurred while copying a configuration file. Migration is expected to occur normally. A backup copy of the previous configuration file is not available.
User Response:
Verify that the user ID has the appropriate file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0228E: The migration function cannot save configuration files; exception {0} occurred.
Explanation:
An unexpected error occurred while trying to save the migrated configuration.
User Response:
Verify that the user ID has sufficient file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0229I: The migration function is updating the attributes of {0} entry {1}. This entry is already defined in the existing model.
Explanation:
The specified entry already exists in the configuration of the new WebSphere Application Server version. The attributes of this entry are being updated.
User Response:
No user action is required.
MIGR0230I: The migration function is ignoring attributes of {0} entry {1}. The objects that are owned by this object are mapped to an appropriate object that is supported by this product.
Explanation:
The specified entry is ignored because it does not directly map to the model of the new Application Server configuration. However, any objects that are owned by this entry are added.
User Response:
No user action is required.
MIGR0232I: No object of type {0} to import.
Explanation:
No objects of the specified type exist to import.
User Response:
No user action is required.
MIGR0234W: The migration function cannot locate object {0} of type {1}.
Explanation:
The migration function cannot locate the object of the specified type when attempting to migrate it.
User Response:
Verify that the object exists in the backup environment that results from the WASPreUpgrade command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0235I: The migration function is completing the configuration import.
Explanation:
The configuration from the prior WebSphere Application Server version is successfully imported into the new WebSphere Application Server version.
User Response:
Inspect the WASPostUpgrade log to verify the results.
MIGR0237I: The migration function read configuration file {0} successfully.
Explanation:
The configuration file was successfully read.
User Response:
No user action is required.
MIGR0241I: Output of {0}.
Explanation:
This message follows another message in the log that shows a different program that is being called during migration. This message displays the results of that call.
User Response:
No user action is required.
MIGR0243I: The data source {0} is already installed in the Java Database Connectivity (JDBC) driver name {1}.
Explanation:
The specified data source is already installed in the Java Database Connectivity (JDBC) driver.
User Response:
No user action is required.
MIGR0244I: The migration function is ignoring the attributes of {0} entry {1}. The entity is already defined in the existing model.
Explanation:
The specified entry is ignored because it does not directly map to the model of the new WebSphere Application Server configuration.
User Response:
No user action is required.
MIGR0249E: An error occurred while updating the plugin-cfg.xml file; exception {0} was caught. Run the GenPlugIncfg command manually.
Explanation:
An error occurred while calling the GenPlugInCfg command at the end of migration. The migration completed normally.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0251I: The migration does not include object {0} of type {1}; it is a Sample.
Explanation:
No Samples are migrated by the WASPostUpgrade command.
User Response:
No user action is required.
MIGR0252W: The migration function cannot restore configuration file {0}. An exception {1} occurred.
Explanation:
While attempting to restore the specified file, an unexpected error occurred. The configuration file might not match the rest of the configuration.
User Response:
If possible, use one of the backup files with the same name to restore the configuration.
MIGR0253E: The backup directory {0} does not exist.
Explanation:
The backup directory that was specified on the command line does not exist.
User Response:
Rerun the command with a valid backup directory that was created by the WASPreUpgrade command.
MIGR0255E: The migration function found an unacceptable substitution value {0}.
Explanation:
The substitution values can be replaced in the input XML file during migration. These values are specified with the WASPostUpgrade command.
User Response:
Rerun the migration command using a valid substitution value.
MIGR0256W: The Lightweight Third Party Authentication (LTPA) AuthMechanism class is not supported by this WebSphere Application Server release. The Simple WebSphere Authentication Mechanism (SWAM) AuthMechanism class is used instead.
Explanation:
The Lightweight Third Party Authentication (LTPA) authentication mechanism is not supported by this release. The Simple WebSphere Authentication Mechanism (SWAM) that is supported by this release is set as the active authentication mechanism.
User Response:
No user action is required.
MIGR0257E: The environment variable {0} was not set.
Explanation:
An internal error occurred. The specified environment variable must be set for the migration command to run.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0258I: The migration function is copying file {0}.
Explanation:
The specified file is being copied.
User Response:
No user action is required.
MIGR0259I: The migration has successfully completed.
Explanation:
The migration has completed with no warning or error messages.
User Response:
No user action is required.
MIGR0260W: {0}{1} has been added to the configuration, but the class path parameter might need to be updated if its prerequisite has changed.
Explanation:
The resource provider is successfully added to the configuration, but its class path information might be incorrect if a prerequisite change is required for the new WebSphere Application Server version.
User Response:
Use the WebSphere Application Server administrative interfaces to update the class path value of the specified resource provider.
MIGR0268W: A failure occurred while updating the server configuration with exception {0}.
Explanation:
An unexpected error occurred while updating the server configuration.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0269E: The call to get configuration settings failed {0}.
Explanation:
An unexpected error occurred while calling an internal program.
User Response:
Verify that the user ID has the sufficient file sytem authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0270E: The call to compute administrative settings failed: {0}.
Explanation:
The call to automatically determine your administrative server name and port failed.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0271W: The migration completed with warnings.
Explanation:
The migration completed with some warning messages, but no errors occurred.
User Response:
For further information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date.
MIGR0272E: The migration function cannot complete the command.
Explanation:
The migration command failed.
User Response:
For additional information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date.
MIGR0275I: {0} is not configured for this node and is not installed.
Explanation:
The specified object was not configured for the migrated node and was not installed.
User Response:
If you need the object installed on the current node, configure and install the object using the WebSphere Application Server administrative interfaces.
MIGR0276E: The -import parameter is not supported for this release and version.
Explanation:
You cannot use the -import parameter when configuration information is stored in a database.
User Response:
Run the command again without the -import parameter.
MIGR0277E: Use the -import parameter to specify the name of your XML file.
Explanation:
The tool cannot find the default XML configuration server-cfg.xml file.
User Response:
Run the command again using the -import parameter to specify the name of your configuration file.
MIGR0278W: {0} applications require source code changes and need manual migration.
Explanation:
You cannot automatically migrate applications that require source code changes.
User Response:
Implement the source code changes and install the applications. Refer to the information center for details.
MIGR0279W: The internationalization service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The other services that are featured in IBM WebSphere Business Integration Server Foundation must be installed to run the specified service.
User Response:
Install the feature, and rerun the command.
MIGR0280W: Application {0} is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The business rule beans that are featured in IBM WebSphere Business Integration Server Foundation must be installed to run business rule beans applications.
User Response:
Install the feature, and rerun the command.
MIGR0281W: All CORBA servers are disabled because the corresponding IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation CORBA C++ SDK must be installed to run CORBA applications.
User Response:
Install the feature, and rerun the command.
MIGR0282W: All defined CORBA servers need to be registered again.
Explanation:
The migration function cannot automatically migrate the CORBA servers.
User Response:
Run the CORBA server registration command for each server that you want to migrate.
MIGR0283E: The migration function cannot read backup options file {0}, exception {1}.
Explanation:
An unexpected error occurred while trying to read the specified file.
User Response:
Verify that the user ID has the sufficient file system authority to run the migration program has sufficient file system authority. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0284E: The version of WebSphere {0} in the specified backup directory cannot be migrated to profile {1}.
Explanation:
The specified backup directory is created from an unsupported version of WebSphere Application Server.
User Response:
Rerun the migration command with a valid backup directory that was created by the WASPreUpgrade command.
MIGR0285E: An unexpected internal error occurred with exception {0}.
Explanation:
An unexpected error occurred.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0286E: The migration failed to complete.
Explanation:
The migration failed to complete because errors occurred during migration.
User Response:
For additional information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date.
MIGR0287I: The migration function successfully created configuration file {0}.
Explanation:
The specified configuration file, which did not exist in the new WebSphere Application Server configuration, is successfully created.
User Response:
No user action is required.
MIGR0288I: Configuration file {0} ready to be saved.
Explanation:
The specified configuration file is ready to be saved.
User Response:
No user action is required.
MIGR0289E: The entry {0} in entry {1} does not exist.
Explanation:
The specified entry in the configuration file does not exist as expected. This configuration file is not valid.
User Response:
Either restore a valid backup from a previous configuration, or use the WebSphere Application Server administrative interfaces to fix the settings in the file.
MIGR0295E: You cannot specify more than {0} positional parameters.
Explanation:
The command that you entered specified more than the maximum number of positional parameters.
User Response:
Check the parameters that are specified on the command and run the command again.
MIGR0296I: The initial heap size setting cannot be mapped because the value might not be valid for this release.
Explanation:
The heap size that is specified in the previous version of WebSphere Application Server does not directly map to the new Application Server model because the servers run in different Java virtual machines. This value is ignored.
User Response:
Check the specified value for the previous version and determine if the heap sizes need updating in the servers of the new configuration.
MIGR0297I: The maximum heap size setting cannot be mapped because it might not be valid for this release.
Explanation:
The heap size that is specified in the previous version of WebSphere Application Server does not directly map to the new Application Server model because the servers run in different Java virtual machines. This value is ignored.
User Response:
Check the specified value for the previous version, and determine if the heap sizes need updating in the servers of the new configuration.
MIGR0300I: The migration function is starting to save the existing WebSphere Application Server environment.
Explanation:
The required steps that save the existing configuration information have started.
User Response:
No user action is required.
MIGR0301I: The existing configuration is being exported.
Explanation:
The configuration information is being read from the database.
User Response:
No user action is required.
MIGR0302I: The existing files are being saved.
Explanation:
The files that you need to restore your configuration on the new release are being copied to the backup directory.
User Response:
No user action is required.
MIGR0303I: The existing WebSphere Application Server environment is saved.
Explanation:
The process of backing up your previous configuration is complete.
User Response:
No user action is required.
MIGR0304I: The previous WebSphere environment is being restored.
Explanation:
The restoration of the previous WebSphere Application Server environment to the configuration of the new WebSphere version has begun.
User Response:
No user action is required.
MIGR0305I: The previous configuration is being imported.
Explanation:
The configuration from the previous WebSphere Application Server version is being imported.
User Response:
No user action is required.
MIGR0307I: The restoration of the previous WebSphere Application Server environment is complete.
Explanation:
The restoration of the previous WebSphere Application Server configuration is complete.
User Response:
Display the WASPostUpgrade log, and verify the results. The message that is displayed before this one indicates success, warning, or error.
MIGR0310E: A value that is specified for {0} is not valid: {1}.
Explanation:
The specified value is incorrect.
User Response:
Consult the help text that is displayed with this message and rerun the command with a correct value.
MIGR0311E: Directory {0} does not exist.
Explanation:
The specified directory does not exist.
User Response:
Create the directory, and rerun the migration command.
MIGR0312E: {0} is not a directory.
Explanation:
The specified value is not a directory.
User Response:
Rerun the command with a valid directory name.
MIGR0313E: More than one {0} directory exists; specify a directory using the {1} parameter.
Explanation:
More than one directory exists in the WebSphere Application Server configuration.
User Response:
Rerun the command specifying the requested directory name by including the noted parameter.
MIGR0314I: The previous configuration of the enterprise extensions is being imported.
Explanation:
The import of configuration information from the previous release has started.
User Response:
No user action is required.
MIGR0315I: The bootstrap port settings are processing.
Explanation:
The bootstrap port settings of the previous WebSphere Application Server version are being processed.
User Response:
No user action is required.
MIGR0316I: The bootstrap port setting is being updated to {0}.
Explanation:
The bootstrap setting of the name server that is associated with the default server is updating to use the same value as in the previous version of WebSphere Application Server.
User Response:
No user action is required.
MIGR0317I: The previous release value of the bootstrap port settings is the default value. No updates occur.
Explanation:
No bootstrap port setting is specified in the previous version of WebSphere Application Server; the current value does not change.
User Response:
No user action is required.
MIGR0318I: The naming context {0} for the enterprise archive (EAR) file {1} is added for interoperability.
Explanation:
The specified naming context is added to the namebindings.xml file.
User Response:
No user action is required.
MIGR0319E: This node is already federated into a cell manager configuration.
Explanation:
This node is already added to the cell manager configuration. Migration does not run because the configuration is controlled by the cell manager.
User Response:
If you want to migrate the node, remove the node from the cell manager configuration, and rerun the command. However, proceed with caution because the configuration is already being managed.
MIGR0323I: {0} is enabled in configuration file {1}.
Explanation:
The specified value is enabled in the configuration file; this value was previously disabled.
User Response:
No user action is required.
MIGR0324E: {0} cannot be enabled in configuration file {1}.
Explanation:
The specified configuration file cannot be enabled.
User Response:
Verify that the user ID has the sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0325I: {0} is converting to {1} in {2}.
Explanation:
The specified object is converting in the specified file.
User Response:
No user action is required.
MIGR0326I: {0} is being added to the {1} file.
Explanation:
The specified object is being added to the specified configuration file.
User Response:
No user action is required.
MIGR0327E: A failure occurred with {0}.
Explanation:
An unexpected error occurred.
User Response:
Verify that the user ID has the sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0331W: Port {0} in file {1} is migrated, but is already assigned in file {2}; this situation might result in port conflicts.
Explanation:
The specified port is already used in the reported file. The port assignment is migrated. The port assignment might cause a conflict if both ports are started at the same time.
User Response:
Use the WebSphere Application Server administrative interfaces to assign unique port values if necessary.
MIGR0332I: The attributes of the {0} authentication mechanism are updating.
Explanation:
The attributes of the specified authentication mechanism are being updated.
User Response:
No user action is required.
MIGR0333W: If you previously enabled security, it has been disabled.
Explanation:
You might need to generate Lightweight Third Party Authentication (LTPA) keys before enabling global security. If global security is enabled, it was disabled during migration.
User Response:
Generate the LTPA keys using the WebSphere Application Server administrative interfaces. Refer to the WebSphere Application Server Information Center for details.
MIGR0334W: If you previously enabled security, it has been disabled. You must configure the Lightweight Third Party Authentication (LTPA) mechanism before enabling security.
Explanation:
The authentication mechanism that was configured in the previous release is not supported by this release. Therefore, if global security was previously enabled, it has been disabled during migration. The only authentication mechanism that is supported is LTPA.
User Response:
To enable security, configure the LTPA authentication mechanism using the WebSphere Application Server administrative interfaces. Refer to the WebSphere Application Server Information Center for details.
MIGR0335I: Attributes of the {0} user registry are updating to reflect the information for server ID {1}.
Explanation:
The attributes of the specified user registry are updated to reflect the information for the specified server ID.
User Response:
No user action is required.
MIGR0337W: The servlet-class attribute of servlet {0} is updating to {1}.
Explanation:
The servlet-class attribute of the specified servlet is updated to reflect the package that contains the servlet for this release. Source code changes might be required to reflect the new package of the specified servlet.
User Response:
No user action is required.
MIGR0338E: The migration function cannot find the server on which to deploy the application {0}.
Explanation:
The tool cannot find servers in the migrated configuration on which to deploy the specified application.
User Response:
Check the migration log file to determine if any servers have successfully migrated. If the correct server exists for the application installation, use the WebSphere administrative interfaces to install the application. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0339I: Application {0} is deploying using the wsadmin command.
Explanation:
The migration function used the wsadmin command to deploy the specified application.
User Response:
No user action is required.
MIGR0340E: Application {0} did not deploy.
Explanation:
The call to the wsadmin command failed, and the specified application is not deployed.
User Response:
To determine why the call to the wsadmin command failed, check the wsadmin.traceout file in the logs directory of the installation root of the new version.
MIGR0341W: The application {0} was not installed. The application is part of a model or server group configuration.
Explanation:
The specified application was not installed on this WebSphere Application Server version because it was part of a model or server group configuration that was migrated.
User Response:
Refer to the WebSphere Application Server Information Center for details.
MIGR0342W: Manual migration is required for file {0}.
Explanation:
Automated migration is not supported for the designated file.
User Response:
Refer to the WebSphere Application Server Information Center for details about how to manually migrate the file.
MIGR0343I: Processing configuration directory {0}.
Explanation:
Starting automated migration for the designated directory.
User Response:
No user action is required.
MIGR0344I: Processing configuration file {0}.
Explanation:
Starting automated migration for the file.
User Response:
No user action is required.
MIGR0345E: The migration backup directory is not compatible with this WebSphere Application Server version.
Explanation:
The migration function cannot apply the version of WebSphere Application Server that is designated as a backup in the specified directory. Either the version in the backup directory is not supported, or the WebSphere products are not compatible.
User Response:
Verify that the combination of WebSphere product types is in the backup directory and that the current versions are compatible.
MIGR0346I: Object {0} of type {1} is not migrating; it is an administrative application.
Explanation:
No administrative applications are migrated during the WASPostUpgrade process.
User Response:
No user action is required.
MIGR0349E: The migration function cannot access the configuration directory.
Explanation:
Another WebSphere Application Server process has a lock on the configuration directory.
User Response:
Close any running WebSphere Application Server processes, and run migration again.
MIGR0350W: Synchronization with the deployment manager using the {0} protocol failed.
Explanation:
The deployment manager might not have been running during migration.
User Response:
Verify that the deployment manager is currently running. Either manually run the syncNode command to update the configuration, or enable the node agent to perform this task automatically the next time that you run the startNode command.
MIGR0351I: The migration function is attempting to synchronize with the deployment manager using the {0} protocol.
Explanation:
The function is trying to connect to the deployment manager using the specified protocol.
User Response:
No user action is required.
MIGR0352I: The synchronization with the deployment manager is successful.
Explanation:
The configuration is successfully synchronized.
User Response:
No user action is required.
MIGR0353E: The migration function cannot create configuration file {0}.
Explanation:
The function cannot create the specified configuration file.
User Response:
Verify that the WASPostUpgrade command has the neccesary permissions to create files, and then try the command again.
MIGR0354W: The WorkArea service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation services feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0355W: The ActivitySession service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0356W: The application profiling service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0357W: The extended messaging service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation extended messaging feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0358W: The object pool service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0359W: The scheduler service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0360W: The staff service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0361W: The work manager service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0362W: The dynamic cache service is disabled because IBM WebSphere Business Integration Server Foundation is not installed.
Explanation:
IBM WebSphere Business Integration Server Foundation must be installed to run the specified service.
User Response:
Install IBM WebSphere Business Integration Server Foundation, and rerun the command.
MIGR0363W: The IBM WebSphere Business Integration adapter service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0364W: The cluster extensions are disabled because IBM WebSphere Business Integration Server Foundation is not installed.
Explanation:
IBM WebSphere Business Integration Server Foundation must be installed to use the cluster extensions.
User Response:
Install IBM WebSphere Business Integration Server Foundation, and run the command again.
MIGR0365W: The member manager service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation member manager feature must be installed to run the specified service.
User Response:
Install the feature, and run the command again.
MIGR0366W: The business process container is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed to use the container.
User Response:
Install the feature, and run the command again.
MIGR0367I: Backing up the current WebSphere Application Server environment.
Explanation:
The existing configuration is saved in the temp directory.
User Response:
No user action is required.
MIGR0368W: Application {0} is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation dynamic query feature must be installed to use the dynamic query service.
User Response:
Install the feature, and run the command again.
MIGR0369E: Synchronization with the deployment manager failed.
Explanation:
The configuration is not successfully synchronized.
User Response:
Either run the synchronization manually, or use deployment manager facilities to perform the synchronization.
MIGR0370I: Property {0} is not migrating to file {1}.
Explanation:
This property is not migrating to the new properties file.
User Response:
No user action is required.
MIGR0371I: The name-value pairs that existed in the old file are not found in the new file.
Explanation:
Leftover properties that are found in the old file are not found in the new file.
User Response:
No user action is required, but you might want to review the file and determine why some properties are missing.
MIGR0372I: Migrated grant permissions follow.
Explanation:
Leftover grants that are found in the old file are not found in the new file.
User Response:
No user action is required.
MIGR0373I: The {0} enterprise application cannot be deployed; the application contains a flow module.
Explanation:
The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed before you can install this enterprise application.
User Response:
Install the enterprise application on the server after installing the feature.
MIGR0374E: Migration of XML document {0} failed, with exception {1}.
Explanation:
An error occurred while migrating the XML file.
User Response:
If the file is corrupted, run the command again with a valid copy of the XML file. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0376I: The dummy key file path {0} that is contained in the SSLConfig attribute {1} is not migrated.
Explanation:
If the dummy key files are used, the path to the key files is not updated. Instead, the new WebSphere Application Server version default path to those files is used.
User Response:
If the dummy key files are modified, refer to the WebSphere Application Server Information Center for details about how to proceed.
MIGR0377W: The dummy key file path {0} that is contained in the SSLConfig attribute {1} has not been migrated.
Explanation:
If the dummy key files are used, the path to the key files is not updated. Instead, the new WebSphere Application Server version default path to those files is used.
User Response:
If the dummy key files are modified, refer to the WebSphere Application Server Information Center for details about how to proceed.
MIGR0378E: The node name of the new configuration must be the same as the old configuration: {0} for this environment.
Explanation:
While migrating a federated node, the node names of the old and new configurations did not match. This configuration cannot be migrated because the old configuration exists in the deployment manager with the old node name. Using the new node name causes an unacceptable configuration in the deployment manager.
User Response:
Uninstall and reinstall WebSphere Application Server using the same node name as the old configuration, or remove the old node from the deployment manager configuration, and manually add this node.
MIGR0379W: Do not use the existing deployment manager in the old configuration. It has been disabled.
Explanation:
The migration of a deployment manager to the latest release is successful. This migration creates the same port definitions as those on the existing WebSphere configuration. Stop the deployment manager of the existing configuration before starting the deployment manager in the new configuration, and do not use it. Use the deployment manager of the new configuration to manage the environment.
User Response:
If you want to use rollback to use the previous WebSphere 5.0 or 5.1 environment instead of WebSphere 6.0 you must re-enable that configuration. To do this go to the /bin directory of the previous WebSphere 5.0 or 5.1 installation and execute the migrationDisablementReversal.jacl script
MIGR0380E: The JMX connection is not established with the deployment manager node {0}, using connector type of {1} on port {2}. The WASPostMigration program is now closing. No changes are made to the local WebSphere Application Server environment.
Explanation:
During a federated migration, a JMX connection must be established with the deployment manager. That connection was not established during this migration attempt.
User Response:
Check the original error message and verify that all the connection information is correct. If the information is correct, verify that the deployment manager is running, and that it is listening on the port that is specified in the error message. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0381E: Migration of the configuration files on the local node failed. The migration is rolling back.
Explanation:
The migration of the configuration files, the properties files, or the policy files has caused an error. All changes are rolling back.
User Response:
Stop any running processes, like the nodeagents or any other process that can interfere with the processing of the configuration files and run migration again. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0382I: The following messages are extracted from the WASPostUpgrade log file on the deployment manager node. You can find a complete listing of messages in the WASPostUpgrade log file.
Explanation:
The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date.
User Response:
No user action is required.
MIGR0383I: This message is the last log message that is extracted from the deployment manager machine.
Explanation:
You can find a complete list of messages in the WASPostUpgrade log file on the deployment manager machine. The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date.
User Response:
No user action is required.
MIGR0384W: The installation failed for one or more applications.
Explanation:
During the application installation process of a federated migration, one or more application installations failed. Refer to the log files for details.
User Response:
If possible, correct the problems that are recorded in the log files. The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date.
MIGR0385I: Starting to save profile {0}.
Explanation:
The series of steps needed to save the existing configuration information for the profile is starting.
User Response:
No user action is required.
MIGR0386E: Profile {0} is not found in the currently installed WebSphere Application Server.
Explanation:
The profile must exist before a migration can be performed.
User Response:
Rerun the command with the correct profile name, or use the wasprofile command to create the correct profile.
MIGR0387E: The backup directory does not contain profile {0}.
Explanation:
The profile did not exist in the previously installed WebSphere.
User Response:
Rerun the command with the correct profile name.
MIGR0388I: Starting migration on the deployment manager node. This may take a few moments, depending on the size and complexity of your configuration.
Explanation:
Inform the user that the migration process has not stalled but is executing on the DeploymentManager node.
User Response:
No user action is required.
MIGR0389I: The application {0} was not installed, the -includeApps attribute was set to false.
Explanation:
When the -includeApps attribute is set to false, no user applications will be installed
User Response:
Install the application using the WebSphere Application Server administration interfaces.
MIGR0390E: The backup directory does not contain a default profile.
Explanation:
A default profile does not exist and the -oldProfile parameter was not specified.
User Response:
Rerun the command with the correct profile name.
MIGR0391I: An application with the same name is already deployed in the configuration; the application {0} was not deployed.
Explanation:
An application with the same name already exists in the configuration.
User Response:
If you want to deploy the migrated application, uninstall the application with the same name and reinstall the application using the WebSphere Application Server administrative interfaces.
MIGR0393E: Unable to update configuration files because of an inconsistency in the configuration.
Explanation:
An inconsistency occurred between the files that the migration updated and the configuration. Most likely some system management interface, for example syncNode, wsadmin and so on, has modified the configuration.
User Response:
Stop the conflicting system management interface and run migration again.
MIGR0394W: IBM WebSphere Web Service Reference service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service.
User Response:
Install the feature and rerun the command.
MIGR0395W: IBM WebSphere Application Event service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service.
User Response:
Install the feature and rerun the command.
MIGR0396W: IBM WebSphere Business Context Data service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
Explanation:
The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service.
User Response:
Install the feature and rerun the command.
MIGR0397W: Service Integration Bus migration failed.
Explanation:
Migration of Embedded JMS to Service Integration Bus failed to execute properly.
User Response:
Please see infocenter for further action, if answer is not found in infocenter please contact IBM support.
MIGR0398E: An unsupported IBM WebSphere Business Integration Server Foundation resource is found in an application.
Explanation:
The application cannot be installed because the required supporting software is not available.
User Response:
No user action is required.
MIGR0399W: The enterprise archive (EAR) file {0} cannot be installed because no deployment targets are specified in the application deployment.xml file.
Explanation:
Deployment targets need to be identified and specified in the application deployment.xml file.
User Response:
Install the application using the WebSphere Application Server administrative interfaces.
MIGR0400I: Server {0} is added to the default core group.
Explanation:
All servers must belong to a core group. This server is added to the default core group.
User Response:
No user action is required.
MIGR0401W: The {0} setting in file {1} is deprecated.
Explanation:
The identified setting is deprecated. This value is still used for this release, but will be removed in a later release.
User Response:
See the information center for further information about an alternative or replacement setting.
MIGR0402I: Existing transports are migrating into the transport channel service; see the information center for further information.
Explanation:
Transports are migrating to corresponding channels in the new release.
User Response:
No user action is required.
MIGR0403I: The transport with a port address of {0} is migrating to channel {1} and belongs to the {2} ThreadPool.
Explanation:
Each transport is migrated to a new channel and belongs to a new default thread pool.
User Response:
No user action is required.
MIGR0404W: Do not use the node agent in the old configuration. It has been disabled.
Explanation:
The migration of a deployment manager to the latest release is successful. This migration creates the same port definitions that are in the existing WebSphere Application Server configuration. The node agent of the existing configuration must be stopped before starting the deployment manager in the new configuration. The deployment manager of the new configuration must be used to manage the environment.
User Response:
If you want to use rollback to use the previous WebSphere 5.0 or 5.1 environment instead of WebSphere 6.0 you must re-enable that configuration. To do this go to the /bin directory of the previous WebSphere 5.0 or 5.1 installation and execute the migrationDisablementReversal.jacl script
MIGR0405E: For additional error details, see {0} on the deployment manager node.
Explanation:
A failure occurred during the federated migration. The deployment manager temp directory contains additional information to resolve the conflict like trace files, log files, configuration files, and so on.
User Response:
If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0406E: The -nodeName parameter must also be provided if the -serverName parameter is provided for this profile type.
Explanation:
The -serverName is provided, but the -nodeName parameter is missing. The profile that is being used has more than one node. The -nodeName parameter must also be provided.
User Response:
Run the command again and provide both parameters.
MIGR0407E: The {0} parameter {1} cannot be found in the profile.
Explanation:
The parameter was specified when running the command. The value that is specified cannot be found in the profile.
User Response:
Run the command again with a correct value for the parameter.
MIGR0408I: The configuration is saved successfully.
Explanation:
The configuration is saved.
User Response:
No user action is required.
MIGR0409E: The currently installed WebSphere does not contain a default profile.
Explanation:
A default profile does not exist and the correct profile parameter was not specified.
User Response:
Rerun the command with the correct profile name.
MIGR0410W: Unable to add server {0} to the default coregroup
Explanation:
All servers must belong to some core group. This server could not be added to the default core group due to some error.
User Response:
The server must be added to some core group before it is able to run. This can be done by using the System Management interfaces.
MIGR0411W: Unable to find a node name in the input configuration that matches the one in the new configuration {0}
Explanation:
While processing the input configuration no node name matches were found that match the one in the new configuration. This means that only data at the cell level will be migrated. No data for nodes, servers or applications will be added to the new configuration.
User Response:
This may be sufficient migration for this configuration but it may not. If it is not then either the existing node name in the new configuration may be incorrect or the input configuration was incorrect. Correct the appropriate values and rerun the WASPostUpgrade command.
MIGR0412W: Node name {0} already exists in the configuration at the current WebSphere Application Server version level. It will not be updated.
Explanation:
While processing a deployment manager configuration a node was attempted to be added to the configuration from the old configuration. However, a node with that name already exists in the configuration at a higher WebSphere Application Server version than exists in the old configuration. It will not be updated.
User Response:
No action required by the user.
MIGR0413W: Node name {0} does not exist in the configuration at the current WebSphere Application Server version level. It will not be updated.
Explanation:
While processing a configuration a node was attempted to be converted from script compatibility mode. However, that node is not at the latest WebSphere Application Server version. It will not be updated.
User Response:
No action required by the user.
MIGR0414E: A failure occurred during migration on the deployment manager node. The migration is rolling back.
Explanation:
While migrating the deployment manager, an error occurred. All changes to the deployment manager node are rolling back.
User Response:
No user action is required.
MIGR0415E: The cell name {0} from the old configuration does not match the cell name {1} in the target profile. No migration can occur.
Explanation:
While processing a deployment manager configuration the cell names of the old and new configurations did not match. This is not a supported migration path
User Response:
Perform migration again using a profile name with the matching cell name.
MIGR0416W: Node name {0} already exists in the configuration at the current WebSphere Application Server version level but it is not the same type of node. It will not be updated.
Explanation:
While processing a configuration a node was attempted to be migrated into the new configuration. However, that node is not the same type in both configurations. One of the nodes is a deployment manager node while the other is a federated node It will not be updated.
User Response:
No action required by the user.
MIGR0417I: Node {0} is added to the default node group.
Explanation:
All nodes must belong to a node group. This node is added to the default node group.
User Response:
No user action is required.
MIGR0418W: A generic server configuration has been migrated. Certain external data that requires manual intervention cannot be migrated.
Explanation:
A generic server manages an external resource. Migration cannot accurately determine which external resources to migrate thus so user intervention is required to back up and verify the setup after migration has is completed.
User Response:
After migration and before you delete the old WebSphere Application Server installation, copy any externally referenced files and perform any kind of application-specific setup that relates to this step.
MIGR0419I: The -useMetaDataFromBinary attribute is set to false for application {0}. The local changes are added to the repository.
Explanation:
Due to limitations in a mixed-node environment, the -useMetaDataFromBinary attribute has been set to false. The local changes that were part of the enterprise archive (EAR) file are also located in the repository, so the behavior of the application does not change.
User Response:
When the application is used for 6.x profiles only, use the administrative console to modify this attribute.
MIGR0420I: The first step of migration completed successfully.
Explanation:
The migration completed with no warning or error messages.
User Response:
No user action is required.
MIGR0421W: The first step of migration completed with warnings.
Explanation:
The migration completed with some warning messages, but no errors occurred.
User Response:
Check the log file that the migration command created in the logs directory, and correct the problems if required. The log name includes a timestamp, so check the log file with the latest creation date.
MIGR0422E: This configuration was disabled during a previously successful migration. Some files might not be saved successfully.
Explanation:
After the previously successful migration, this configuration was disabled so that it would not interfere with the new configuration.
User Response:
If you need to migrate this configuration again, use the migrationDisablementReversal.jacl file in the bin directory to enable the configuration, and then run this command again.
MIGR0423W: The deployment manager node has changed from {0} to {1}; this situation can cause some side effects, including a requirement to restart all the node agents.
Explanation:
The deployment manager node has a different name in the old configuration than in the new configuration. This name can work, with some side effects. One side effect is that all the node agents that are accessing this configuration must be restarted to communicate. The node name is part of the communications properties. Another side effect can affect administration scripts that are created by users. If these scripts reference the deployment manager node name, they need modification.
User Response:
If you do not want this change, create a new profile where the deployment manager node name matches the name in the old configuration and run the migration against this new profile.
MIGR0424E: The deployment manager has not been migrated.
Explanation:
The deployment manager must be migrated before you can migrate managed nodes.
User Response:
Run the migration utilities to migrate the deployment manager first and then try your managed node migration again. See the WebSphere Application Server Information Center for detailed steps.
MIGR0425I: A deployment manager migration is detected. Before continuing with the WASPostUpgrade process, run the backupConfig command on your federated nodes.
Explanation:
Certain files in the V5 environment might be modified during the migration of a V6 deployment manager that manages V5 nodes. By running the backupConfig command against your V5 environment, you provide yourself with an error recovery path.
User Response:
Run the backupConfig command against all the V5 nodes that are managed by the V6 deployment manager.
MIGR0426E: {0} command not supported on z/OS for direct invocation from the Unix shell. Use the WebSphere z/OS Customization Dialog migration option instead.
Explanation:
The direct invocation of WASPreUpgrade and WASPostUpgrade is not supported.
User Response:
Use the WebSphere z/OS Customization Dialog migration option to invoke the migration utilities.
MIGR0900E: The specified command is not valid.
Explanation:
This problem is usually caused by parameters that are misspelled or missing.
User Response:
Verify that all of the parameters are valid and spelled correctly. Type the command without parameters or arguments to get the correct syntax of the command.
MIGR0901W: You must use the -traceString parameter with the -traceFile parameter.
Explanation:
When you specify a file trace, you must also specify the level of detail to write out to trace through the -traceString parameter.
User Response:
Add the -traceString parameter. For example: -traceString "*=all=enabled" You must include the quotation marks.
MIGR0903W: A value for attribute {0} is missing.
Explanation:
No argument is provided for the specified attribute. For example, the parameter '-traceFile' was used, but '-traceFile /some/path/to/log/file.txt' was required.
User Response:
Supply an argument for the specified parameter.
MIGR0904W: The enterprise archive (EAR) file {0} is not valid.
Explanation:
The enterprise archive (EAR) file name is either not an EAR file, or the contents and structure of the EAR file do not follow the Java 2 Platform, Enterprise Edition (J2EE) specification.
User Response:
Verify that the path is spelled correctly, and that a valid EAR file is in that location.
MIGR0905W: An unacceptable parameter was specified {0}.
Explanation:
A specified parameter is not recognized as a valid parameter.
User Response:
Verify spelling and run the command alone, without any parameters or arguments, to get the correct syntax of the command.
MIGR0906W: You must specify the enterprise archive (EAR) file location.
Explanation:
No enterprise archive (EAR) file is specified. This file name is the first argument that you pass in after the command. For example: clientUpgrade /ear/file/location/earfile.ear
User Response:
Rerun the command with an EAR file as the first argument.
MIGR0907W: The enterprise archive (EAR) file {0} does not exist.
Explanation:
Cannot find the specified EAR file in the given location.
User Response:
Verify that the path is spelled correctly and that an EAR file exists in that location.
MIGR0908W: The enterprise archive (EAR) file name {0} is a directory.
Explanation:
The specified enterprise archive (EAR) file is a directory.
User Response:
Verify that the specified EAR file is an EAR file and not a directory.
MIGR0909W: No client Java archive (JAR) files are found by the name {0}.
Explanation:
The enterprise archive (EAR) file does not contain any client Java archive (JAR) files by the specified name.
User Response:
Verify that the EAR file contains the client JAR file that is specified.
MIGR0910W: No client Java archive (JAR) files are found.
Explanation:
The enterprise archive (EAR) file does not contain any client JAR files.
User Response:
If the specified EAR file is expected to contain client Java archive (JAR) files, correct the EAR file, and try the command again.
MIGR0911I: All of the client Java archive (JAR) files are being migrated.
Explanation:
No client Java archive (JAR) file was specified for migration, so all of the client JAR files are migrated.
User Response:
No user action is required.
MIGR0912I: The client Java archive (JAR) file migration on {0} is running.
Explanation:
This client Java archive (JAR) file is in the process of migrating.
User Response:
No user action is required.
MIGR0913E: An undefined error occurred during the client upgrade process.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0914E: An error occurred during trace setup.
Explanation:
The trace cannot be properly set up. The trace might not be working.
User Response:
If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/
MIGR0915I: The Java archive (JAR) file {0} was previously migrated and is not modified now.
Explanation:
This tool has already migrated the enterprise archive (EAR) file or the JAR file that you attempted to migrate. The file is not modified.
User Response:
No user action is required.
MIGR0916W: {0} already exists in a 5.0.x or 5.1.x format, and is not migrated.
Explanation:
The Java archive (JAR) file that you attempted to migrate already exists in a 5.0.x or a 5.1.x format.
User Response:
No user action is required.