Express (Distributed operating systems), v8.0 > Reference > Messages
MIGR
MIGR0001I: The class name of the WASPreUpgrade command is WASPreUpgrade
Explanation None Action No user action is required.
MIGR0002I: The class name of the WASPostUpgrade command is WASPostUpgrade
Explanation None Action No user action is required.
MIGR0102E: An unsupported command line parameter was used.
Explanation The command parameters are incorrectly specified. Action Verify that all of the parameters are valid and spelled correctly.
MIGR0103E: We must specify the backup directory name.
Explanation The backup directory is used to store the configuration information that is migrated to the new release. Action Run the command again and specify the backup directory.
MIGR0104E: We must specify the currently installed Application Server directory name.
Explanation We must access the currently installed Application Server directory to obtain the configuration information that is migrating to the new release. Action Run the command again and specify the currently installed Application Server directory.
MIGR0106E: The illegal argument {0} is specified.
Explanation The specified parameter is not supported by the command. Action 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. Action 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 Application Server v5.1 and later. Action 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 Application Server is not supported by this command.
Explanation The WASPostUpgrade command is running against an unsupported version of Application Server. The WASPostUpgrade command that was invoked might not be using the current version of the Application Server directories. Action Invoke the command in the current Application Server directory structure.
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. Action Run the command again and specify the name of a directory.
MIGR0112E: The specified backup directory cannot be used because it is not writable.
Explanation Specify a writable directory so that files containing the configuration information for the current release can be saved. Action 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 specified. Action Determine why the directory cannot be created and run the command again. If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action See the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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 Application Server program; the call cannot be successfully completed. Action If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
MIGR0117E: The specified Application Server directory does not contain a valid product file {0}.
Explanation The specified directory on the migration command does not contain a valid <samp>properties/com/ibm/websphere/product.xml </samp> file. Action Rerun the command with a valid Application Server XML file name.
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. Action Rerun the command with a valid XML import file.
MIGR0122E: The migration function cannot read configuration file {0}.
Explanation The function cannot read the specified configuration file. Action If the file is part of the current 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 and have 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. Action See the following errors in the migration log for further details. Correct the problem and rerun the command, or use the Application Server 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. Action Verify that the file exists, and rerun the command.
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. Action 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. Action Check the user file permissions before you run the command again.
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. Action If this source file must be used to create an enterprise application, use a development environment like the Rational 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. Action If the directory must be used to create an enterprise application, use a development environment like the Rational Application Developer to add the files from that directory to the appropriate location in the enterprise application.
MIGR0210I: The migration function is creating a directory {0}.
Explanation The directory was created during normal processing. Action No user action is required.
MIGR0211I: The migration function is copying a directory {0}.
Explanation The function is copying a directory and its contents. Action 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. Action 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. Action Verify that the user ID has sufficient file system authority to run the migration command.
MIGR0214W: The migration function cannot copy the file. Source {0} does not exist.
Explanation An unexpected failure occurred when a configuration file was copied. Action If the source file must be used to create an enterprise application, use a development environment such as the Rational 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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0221I: The migration function is reading the previously saved configuration file {0}.
Explanation The specified configuration file from a previous Application Server version is being read. This file is the source for importing objects into the new Application Server configuration. Action No user action is required.
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 Application Server version. Action No user action is required.
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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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 Application Server version. The attributes of this entry are being updated. Action 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. Action 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 Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0237I: The migration function read configuration file {0} successfully.
Explanation The configuration file was successfully read. Action 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. Action No user action is required.
MIGR0249E: An error occurred while updating the <samp>plugin-cfg.xml </samp> 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. Action If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action 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. Action 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. Action Rerun the command with a valid backup directory 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. Action Rerun the migration command using a valid substitution value.
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. Action If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0259I: The migration has successfully completed.
Explanation The migration has completed with no warning or error messages. Action No user action is required.
MIGR0271W: Migration completed successfully, with one or more warnings.
Explanation The migration completed with some warning messages, but no errors occurred. Action For further information; check the log file 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. Action For additional information; check the log file 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.
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. Action 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. Action Install the feature, and rerun the command.
MIGR0283E: The migration function cannot read backup options file {0}, exception {1}.
Explanation An unexpected error occurred while trying to read the specified file. Action Verify that the user ID has sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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 Application Server. Action Rerun the migration command with a valid backup directory created by the WASPreUpgrade command.
MIGR0285E: An unexpected internal error occurred with exception {0}.
Explanation An unexpected error occurred. Action If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action For additional information; check the log file 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 Application Server configuration, is successfully created. Action No user action is required.
MIGR0288I: Configuration file {0} ready to be saved.
Explanation The specified configuration file is ready to be saved. Action 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. Action Either restore a valid backup from a previous configuration, or use the Application Server administrative interfaces to fix the settings in the file.
MIGR0300I: The migration function is starting to save the existing Application Server environment.
Explanation The required steps that save the existing configuration information have started. Action No user action is required.
MIGR0302I: The existing files are being saved.
Explanation The files that restore the configuration on the new release are being copied to the backup directory. Action No user action is required.
MIGR0303I: The existing Application Server environment is saved.
Explanation The process of backing up your previous configuration is complete. Action No user action is required.
MIGR0304I: The previous WebSphere environment is being merged into this profile.
Explanation The migration of the previous Application Server environment to the configuration of the new WebSphere version has begun. Action No user action is required.
MIGR0307I: The restoration of the previous Application Server environment is complete.
Explanation The restoration of the previous Application Server configuration is complete. Action Display the WASPostUpgrade log, and verify the results. The message that is displayed before this one indicates success, warning, or error.
MIGR0310E: A value specified for {0} is not valid: {1}.
Explanation The specified value is incorrect. Action Consult the help text that is displayed with this message, and rerun the command with a correct value.
MIGR0313E: More than one {0} directory exists; specify a directory using the {1} parameter.
Explanation More than one directory exists in the Application Server configuration. Action Rerun the command specifying the requested directory name by including the noted parameter.
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. Action 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.
MIGR0327E: A failure occurred with {0}.
Explanation An unexpected error occurred. Action Verify that the user ID has sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. Action Use the 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. Action No user action is required.
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. Action No user action is required.
MIGR0339I: Application {0} is deploying using the wsadmin command.
Explanation The migration function used the wsadmin command to deploy the specified application. Action No user action is required.
MIGR0340W: Application {0} did not deploy.
Explanation The call to the wsadmin command failed, and the specified application is not deployed. Action To determine why the call to the wsadmin command failed, check the <samp>wsadmin.traceout </samp> file in the logs directory of the installation root of the new version.
MIGR0341W: Application installation directory has been updated to {0}.
Explanation The specified value application installation directory has been updated to use the common WebSphere variables Action No action is required,
MIGR0344I: Processing configuration file {0}.
Explanation Automated migration for the file is starting. Action No user action is required.
MIGR0345E: The migration backup directory is not compatible with this Application Server version.
Explanation The migration function cannot apply the version of 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. Action 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. Action No user action is required.
MIGR0349E: The migration function cannot access the configuration directory.
Explanation Another Application Server process has a lock on the configuration directory. Action Close any running Application Server processes, and run migration again.
MIGR0350W: Synchronization with the dmgr using the {0} protocol failed.
Explanation The dmgr might not have been running during migration. Action Verify that the dmgr 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 dmgr using the {0} protocol.
Explanation The function is trying to connect to the dmgr using the specified protocol. Action No user action is required.
MIGR0352I: The synchronization with the dmgr is successful.
Explanation The configuration is successfully synchronized. Action No user action is required.
MIGR0353E: The migration function cannot create configuration file {0}.
Explanation The function cannot create the specified configuration file. Action Verify that the WASPostUpgrade command has the necessary permissions to create files, and then try 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. Action 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. Action Install the feature, and run the command again.
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. Action Install the feature, 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. Action 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. Action Install the feature, and run the command again.
MIGR0367I: Backing up the current Application Server environment.
Explanation The existing configuration is saved in the <samp>temp </samp> directory. Action 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. Action 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. Action No user action is required.
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 dmgr with the old node name. Using the new node name causes an unacceptable configuration in the dmgr. Action Uninstall and reinstall Application Server using the same node name as the old configuration, or remove the old node from the dmgr configuration and manually add this node.
MIGR0379W: Do not use the existing dmgr in the old configuration. It has been disabled.
Explanation The migration of a dmgr to the latest release is successful. This migration creates the same port definitions as those on the existing Application Server configuration. Stop the dmgr of the existing configuration before starting the dmgr in the new configuration, and do not use it. Use the dmgr of the new configuration to manage the environment. Action To roll back to use the previous Application Server v5.1, 6.0 or 6.1 environment instead of v7.0, re-enable that configuration. To do this, go to the /bin directory of the previous v5.1 6.0 or 6.1 installation and run the migrationDisablementReversal.jacl script.
MIGR0380E: The JMX connection is not established with the dmgr node {0}, using connector type of {1} on port {2}. The WASPostMigration program is now closing. No changes are made to the local Application Server environment.
Explanation During a federated migration, a JMX connection must be established with the dmgr. That connection was not established during this migration attempt. Action Check the original error message and verify that all the connection information is correct. If the information is correct, verify that the dmgr is running, and that it is listening on the port specified in the error message. If the problem persists, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
MIGR0385I: Starting to save profile {0}.
Explanation The series of steps needed to save the existing configuration information for the profile is starting. Action No user action is required.
MIGR0386E: Profile {0} is not found in the currently installed Application Server.
Explanation The profile must exist before a migration can be performed. Action 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. Action Rerun the command with the correct profile name.
MIGR0389I: Applications will not be migrated, the -includeApps attribute was set to false.
Explanation When the -includeApps attribute is set to false, no user applications are installed on the new version. Action Install the application using the 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. Action Rerun the command with the correct profile name.
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. Action 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. Action 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. Action Install the feature, and rerun the command.
MIGR0397W: Service Integration Bus migration failed.
Explanation The migration of Embedded JMS to Service Integration Bus failed to migrate properly. Action See the information center for further action; if the answer is not found in the information center, 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. Action No user action is required.
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. Action No user action is required.
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. Action 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. Action 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 dmgr to the latest release is successful. This migration creates the same port definitions that are in the existing Application Server configuration. The node agent of the existing configuration must be stopped before starting the dmgr in the new configuration. The dmgr of the new configuration must be used to manage the environment. Action To roll back to use the previous Application Server v5.1, 6.0 or 6.1 environment instead of v7.0, re-enable that configuration. To do this go to the /bin directory of the previous v5.1, 6.0 or 6.1 installation and run the migrationDisablementReversal.jacl script.
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. Action 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 specified cannot be found in the profile. Action Run the command again with a correct value for the parameter.
MIGR0408I: The configuration is saved successfully.
Explanation The configuration is saved. Action 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. Action 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. Action 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.
MIGR0412W: Node name {0} already exists in the configuration at the current Application Server version level. It will not be updated.
Explanation While processing a dmgr configuration, an attempt was made to add a node to the configuration from the old configuration. However, a node with that name already exists in the configuration at a higher Application Server version than exists in the old configuration. It will not be updated. Action No user action is required.
MIGR0413W: Node name {0} does not exist in the configuration at the current Application Server version level. It will not be updated.
Explanation While processing a configuration, an attempt was made to convert a node from script compatibility mode. However, that node is not at the latest Application Server version. It will not be updated. Action 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 dmgr configuration the cell names of the old and new configurations did not match. This is not a supported migration path. Action Perform migration again using a profile name with the matching cell name.
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. Action No user action is required.
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 EAR file are also located in the repository, so the behavior of the application does not change. Action When the application is used for Application Server v6.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. Action 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. Action Check the log file that the migration command created 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.
MIGR0425I: A dmgr migration is detected. Before continuing with the WASPostUpgrade process, run the backupConfig command on your federated nodes.
Explanation Certain files in the Application Server v5 or 6 environment might be modified during the migration of a version 7 dmgr that manages version 5 or 6 nodes. By running the backupConfig command against your version 5 or 6 environment, provided yourself with an error recovery path. Action Run the backupConfig command against all the version 5 or 6 nodes that are managed by the version 7 dmgr.
MIGR0426E: {0} command not supported on z/OS for direct invocation from the Unix shell. Use z/OS Migration Management Tool under WebSphere Customization Tools instead.
Explanation The direct invocation of WASPreUpgrade and WASPostUpgrade is not supported. Action Use z/OS Migration Management Tool under WebSphere Customization Tools to create your migration definitions.
MIGR0427W: Node {0} has been migrated, but may not be manageable in current release.
Explanation This release of Application Server cannot manage nodes prior to v6.0.2.0 without a fix. Action Install the required fix to v6.0.0.x and 6.0.1.y nodes prior to migration.
MIGR0428E: Incorrect Deployment Manager connection established.
Explanation The dmgr to which this node belongs is not the dmgr currently running. Action Shut down the incorrect dmgr, and start the dmgr that is currently managing the node to be migrated.
MIGR0429I: Cloudscape Database {0} was successfully migrated. See log {1}
Explanation The migration of Cloudscape to Derby was successfully for this particular database. Action No user action is required.
MIGR0430W: Cloudscape Database {0} failed to migrate to {1} Database. See log {2}
Explanation The migration of Cloudscape to Derby has failed for this particular database. Action Manual migration of the old dataBase to new database is required. See the information center details.
MIGR0431E: Federated node {0} already exists in current configuration. Migration cannot continue.
Explanation This error occurs if the new dmgr configuration contains a node with the same name as a node in the prior release. This happens if the user does an "addNode" in the current release prior to migration. Action UnFederate the node in the current release, and rerun migration.
MIGR0432W: Found server {0} to be of type {1} which is unsupported in current product version. {0} will not be migrated.
Explanation This error occurs when an unsupported server type is encountered. Action Use the migration utilities for the product that this server type belongs too.
MIGR0433E: Conflicting parameters, -keepAppDirectory true and -appInstallDirectory, have both been specified. If -appInstallDirectory is specified, -keepAppDirectory must be false.
Explanation This error occurs when -keepAppDirectory true and -appInstallDirectory are both specified. Action Select only one of the two parameters, or specify -keepAppDirectory false.
MIGR0434I: Will not be migrating object {0} of type {1}, it is already installed.
Explanation Applications that are already installed in the new profile will not be migrated. Action No user action is required.
MIGR0435W: Could not resolve variable {0}.
Explanation A variable being used could not be resolved using the defined variables Action Check to see if the variable is being used for a valid reason. If not then no further action is required; if it is, then define the variable.
MIGR0436W: Could not process resource {0} due to variable issues.
Explanation A variable being used could not be resolved using the defined variables Action Check to see if the variable is being used for a valid reason. If not then no further action is required; if it is, then define the variable.
MIGR0437E: Detected current version of dmgr running while -keepDMgrEnabled attribute set.
Explanation To avoid having two dmgrs managing the same cell, shut down the current version of dmgr when specifying -keepDMgrEnabled=true Action Shut down the current version of dmgr, and perform the migration again.
MIGR0438W: Not copying file or directory {0} because a version of the file or directory already exists in current version.
Explanation The file or directory might already exist. To avoid overwriting a valid file or directory, the file or directory will not be copied. Action If the file or directory is required, then manually search the WASPreUpgrade backup directory for the file or directory and copy it into the new environment.
MIGR0439E: Can not initialize trace services.
Explanation Verification of the -traceFile location failed. Action Make sure that the -traceFile location is not write protected and that the path entered is a valid path.
MIGR0440W: The migration of one or more applications terminated unexpectedly.
Explanation During the application migration process, one or more applications failed to migrate. Refer to the log files for details. Action If possible, correct the problems that are recorded in the log files. One or more applications might need to be installed manually.
MIGR0441I: The migration function is copying {0} entry {1} to the model.
Explanation The specified object is being copied to the configuration of the new Application Server version. Action No user action is required.
MIGR0443E: {0} {1} does not exist, will not continue.
Explanation The node or server name specified does not exist. Action Run the command again and specify existing node and server names.
MIGR0444W: Cell-level documents are not merged. Any changes that you make to the stand-alone cell-level documents before using the WASPostUpgrade command must be repeated on the new cell. For example, virtual hosts.
Explanation During a managed node migration, any new v7 configuration changes that existed prior to running WASPostUpgrade might need to be reapplied after the WASPostUpgrade process completes. Action Reapply preexisting v7 cell level changes after the managed node migration has been completed.
MIGR0445W: The JDBC provider, {0}, is no longer a valid. You will not be able to create any new data sources for this provider until you either use the WebSphereConnectJDBCDriverConversion tool or create a new JDBC provider.
Explanation A JDBC provider in the previous version did not have a provider type defined. This is a required attribute. The provider type could not be resolved during migration. Action Ensure that each JDBCProvider has a providerType. For WebSphere Connect JDBC providers, consider using the WebSphereConnectJDBCDriverConversion tool. For all other providers, IBM recommends that it be deleted, unless we have previously configured data sources that still use it.
MIGR0446I: Port conflicts were resolved during migration as shown below for document: {0}
Explanation The Application Server migration tooling updated the values of network ports. The resulting port values are listed for each file. All port settings for the document are listed even if they were unchanged. Action The Application Server migration tooling changed port settings to ensure that migrated values did not conflict with settings in the existing configuration. We can update the port settings using the administrative console or the wsadmin scripting interface as required by the environment.
MIGR0449I: The following ports were not changed as part of migration because no migrated servers contained these values.
Explanation Configurations can contain port listings that are not bound by servers at startup--for example, host aliases in a virtual host. If the ports are not part of a server that was migrated during this Migration, the values will not be changed. Action Update references to these unmodified ports manually as needed by the environment to resolve port conflicts. Use the Application Server administrative interfaces or the wsadmin scripting interface to update these values.
MIGR0450W: Some files were copied directly without being processed by migration, review MIGR0451W messages in the log file.
Explanation The Application Server migration tooling did not process some files that were saved during WASPreUpgrade. This is part of tooling to support migration from one machine to another and is an expected message when migrating to a different machine Action Review the log from migration WASPostUpgrade, and check for MIGR0451W messages in the log file.
MIGR0451W: Migration copied file originally located at {0} to local path {1}
Explanation Migration copied the file because it had not already been processed during migration. Action No user action is required.
MIGR0452W: Migration could not locate a file matching {0} when migrating {1}. The reference has not been modified.
Explanation Migration found a reference to a file that could not be found as part of migration. This means the file was either not backed up during WASPreUpgrade or not copied forward during WASPostUpgrade. Action Copy the missing file to the location specified and rerun migration, or update the reference after migration has completed.
MIGR0453W: Not migrating DB2 for zOS Local JDBC Provider (RRS) JDBC Provider. This JDBC Provider will be copied over as-is but will be disabled at runtime. In order for this JDBC Provider to function at runtime it will need to be migrated to a DB2 Universal JDBC Driver Provider using the DB2 Universal Driver. This can be done manually or by using the IBM Application Server JDBC Migration Utility for DB2 on z/OS, available as a web download. Contact IBM support for details.
Explanation The DB2 for zOS Local JDBC Provider (RRS) JDBC provider is not supported in the targeted Application Server version. Action Manually create the DB2 Universal Driver provider.
MIGR0454I: The {0} setting in file {1} is deprecated.
Explanation The identified setting is deprecated. This value is still used for this release, but it will be removed in a later release. Action See the information center for information about an alternative or replacement setting.
MIGR0455W: WebSphere Connect JDBC driver support has been removed. Data source {0} will need to be modified to make use of either Microsoft SQL Server JDBC Driver or DataDirect Connect JDBC driver.
Explanation WebSphere Connect JDBC driver support has been removed. Any WebSphere Connect type data sources need to be modified to use either the Microsoft SQL Server JDBC Driver or DataDirect Connect JDBC driver. Action See the information center for information about an alternative or replacement setting.
MIGR0456W: Do not use the existing dmgr in the old configuration.
Explanation The migration of a dmgr to the latest release is successful. This migration creates the same port definitions as those on the existing Application Server configuration. Stop the dmgr of the existing configuration before starting the dmgr in the new configuration. Use the dmgr of the new configuration to manage the environment. Action To use the old environment, restart the prior version Deployment Manager.
MIGR0457W: Do not use the node agent in the old configuration.
Explanation The migration of the Managed node to the latest release is successful. This migration creates the same port definitions that are in the existing Application Server configuration. The node agent of the existing configuration must be stopped before starting the dmgr in the new configuration. The dmgr of the new configuration must be used to manage the environment. Action To use the old environment you will need to restart the prior version of the Deployment Manager and Managed node.
MIGR0458E: Security is enabled in your prior configuration. -username and -password are required arguments.
Explanation WASPostUpgrade requires the user name and password to perform administrative functions against the prior configuration. Action Rerun WASPostUpgrade and supply the user name and password of your prior configuration.
MIGR0459I: Application Server configuration files are being migration.
Explanation This indicates that a specific backup of Application Server files are being migrated into this configuration. Action No user action is required.
MIGR0460E: Application Server migration is not supported in this configuration.
Explanation This indicates that the specified backup cannot be migrated into this profile. Additional information can be found in other messages printed to the migration log files. Action Resolve the issues causing the other failing messages, and then rerun the migration.
MIGR0461I: Application Server has already been migrated.
Explanation This indicates that the base Application Server files have already been migrated. They will not be migrated again. Action No user action is required.
MIGR0462I: Application Server factor is saving base configuration files.
Explanation This indicates that a backup of the existing configuration is being saved for use during the WASPostUpgrade step of migration. Action No user action is required.
MIGR0463I: Nothing to migrate at this time. The current profile has already been migrated with all information from enabled features.
Explanation This message indicates that all features in the backup directory that are enabled in the current configuration have already been migrated. If information that you expected is not available in the current configuration, review the installed products and ensure that the correct features are installed. Action No user action is required.
MIGR0464E: Failed to stop prior release nodeagent.
Explanation This indicates that we were unsuccessful in stopping the prior release nodeagent. Migration will not continue. Action Shut down nodeagent of prior release and perform Migration again.
MIGR0465E: Error in command line after {0}, found unexpected text {1}. All optional parameters must be prefixed by a label escaped by a leading - character.
Explanation
Optional parameters must be prefixed by the escape character '-' and have at most one string argument.Action Verify that the proper optional parameter syntax is being used. Review the command line help for more information.
MIGR0466E: No value was found for the argument {0}. This argument requires a value{1}.
Explanation This optional parameters require an argument. Action Verify that the proper optional parameter syntax is being used. Review the command line help for more information.
MIGR0467W: A user defined data source helper {0} has been detected. It will be migrated, but it must be reimplemented to work correctly.
Explanation Your data source helper will need to be reimplemented to inherit from ConnectJDBCDataStoreHelper or MicrosoftSQLServerDataStoreHelper. Action Reimplement data source helper to inherit from ConnectJDBCDataStoreHelper or MicrosoftSQLServerDataStoreHelper. See the information center for more details.
MIGR0468W: Adding properties unique to the Microsoft SQL Server JDBC Driver. Review the default values to ensure the desired behavior.
Explanation Adding properties unique to the Microsoft SQL Server JDBC Driver. Review the default values to ensure the desired behavior. Action See information center for further details.
MIGR0469W: Removing properties unique to the WebSphere Connect JDBC driver. These features are no longer available:
Explanation Properties do not have a direct mapping from DataDirect data source to Microsoft data source thus will be dropped. Action See information center for further details.
MIGR0471W: Property {0} has been modified or replaced to conform to Microsoft SQL Server JDBC Driver requirements. Validate changes made.
Explanation Property has been modified to conform to Microsoft data source requirements. These changes should be validated for correctness on the system. Action See information center for further details.
MIGR0472I: Converting WebSphere Connect JDBC Provider "{0}" to {1} Provider.
Explanation Performing conversion on WebSphere Applilcation Server DataDirect resource. Action None
MIGR0473I: Converting WebSphere Connect JDBC driver data source "{0}" to {1} data source.
Explanation Performing conversion on WebSphere Applilcation Server DataDirect resource. Action None
MIGR0474I: Do not remove this property until all Federated nodes have been migrated to v7.x and all application have been tested against the Microsoft driver.
Explanation This property is needed by XSL Transforms to down convert configuration data to pre v7.x Federated nodes. Action Once all Federated nodes have been migrated to v7.x and all applications have been tested against the Microsoft driver you can then safely remove this property.
MIGR0476E: This command is required to be run against the Deployment Manager's configuration and the changes manually sychronize to the Managed nodes.
Explanation It was detected that the command was run against a Managed node's configuration. The command needs to be run against the Deployment Manager's configuration. Action Run command against the Deployment Managers's configuration.
MIGR0477I: The Deployment Manager's configuration has been updated. A synchronization with the effected Managed nodes must occur before using these updated settings.
Explanation The Deployment Manager's configuration has been updated, but in order to have the settings consistent a synchronization must occur either automatically by the Deployment Manager or manually invoked. Action Synchronize the Deployment Manager's configuration with the effected Managed nodes.
MIGR0478E: The port value for the endpoint {0} in of the server {1} is invalid or missing.
Explanation Invalid port information exist for the specified entry. This information is required for migration processing. Action Correct the port information for the specified server in the serverindex in the master repository (which resides on the Deployment Manager in distributed configurations), and then rerun migration.
MIGR0479E: The host value for the endpoint {0} in of the server {1} is invalid or missing.
Explanation Invalid host information exist for the specified entry. This information is required for migration processing. Action Correct the host information for the specified server in the serverindex in the master repository (which resides on the Deployment Manager in distributed configurations), and then rerun migration.
MIGR0480E: The node {0} specified for the -nodeName parameter is not at the current release. Migrate node to current release and run tool again.
Explanation Tool will only work against nodes that have been migrated and are at the current release level. Action Migrate your node to the current release level and then run the tool again.
MIGR0481E: The {0} {1} specified for the {2} parameter does not exist.
Explanation Could not find node or server in the configuration. Most likely cause is that the node or server name was misspelled. Action Verify node or server name was spelled correctly.
MIGR0482E: We must specify the <backupDirectoryName> and <currentWebSphereDirectory>.
Explanation WASPreUpgrade requires that the <backupDirectoryName> and <currentWebSphereDirectory> be specified. Action Run WASPreUpgrade again supplying the required parameters.
MIGR0483W: Variable {0} at {1} scope has been defined with an emtpy value. This variable has also been defined at a broader scope. The broader scoped variable value will be hidden.
Explanation A variable has been redefined at a narrower scope which will override the broader scoped value. Action Remove the offending variable from the narrower scope or replace the narrower scoped variables value with the broader scoped variables value.
MIGR0484E: No profiles or instances found with name {0}.
Explanation WASPreUpgrade command did not find any profiles or instances with the name specified. Action Run WASPreUpgrade command again specifying a profile or instance name that exists.
MIGR0485W: Process count exceeds the maximum recommended limit of {0} processes per coregroup.
Explanation Performance may degrade with coregroups of large size. Action Redistribute coregroup processes to smaller coregroup groupings.
MIGR0486I: The {0} setting in file {1} is deprecated.
Explanation The identified setting is deprecated. This value is still used for this release, but it will be removed in a later release. Action See the information center for information about an alternative or replacement setting.
MIGR0487I: The {0} parameter not required in this scenario, and is being ignored.
Explanation The identified parameter is not needed for the current migration. Action No action is neccessary.
MIGR0488E: The dmgr node name in the new configuration ({0}) cannot be the same as a nodeagent node in the old configuration.
Explanation While migrating a dmgr node, the node names of the dmgr in the new configuration must either be unique from all nodes in the old configuration or be identical to the dmgr node name in the old release. Action Create a new dmgr profile in the new configuration where the node name for the dmgr matches the node name from the old configuration.
MIGR0489E: The migration backup directory profile is of type {0} which is not compatible with this profile type {1}.
Explanation The migration requires that compatible profile types be used when migrating. Of note, it is not possible to migrate into a target profile that is already federated into a Deployment Manager. Action Create a new profile of a compatible type; specify a different profile to migrate; or use the Migration wizard, the z/OS Migration Management Tool, or the zMMT command to create the target profile automatically.
MIGR0490I: Changing the {0} setting from {1} to {2} in the file {3} to meet performance requirements.
Explanation The migration has adjusted a value that was configured outside the recommended minimum or maximum for the specified performance tuning option. Action Customers should be aware that the migrated server may require more resources than previous releases. The change has been made to conform to recommended values, but if you determine that this is beyond the needs of the system you may change the value.
MIGR0491W: The migration function cannot continue because there are too many open files.
Explanation The number of open files is limited by the operating system, and the current setting has insufficient file handles for running migration program. Action Configure more available file descriptors in the session that runs the migration program, and restart the migration.
MIGR0492W: The SOAP port has changed from {0} to {1}, manually synchronize the managed nodes with the Deployment Manager.
Explanation The Deployment Manager's SOAP_CONNECTOR_ADDRESS port number has been changed, in order for the managed nodes to communicate with the Deployment Manager, a manual synchronization must occur using new SOAP_CONNECTOR_ADDRESS port number. Action Run syncNode from the effected Managed nodes using new SOAP_CONNECTOR_ADDRESS port number. See the InfoCEnter for more information about executing syncNode manually with port information.
MIGR0493E: The profile name {0} does not match the target profile {1}, the profile names must match for this migration.
Explanation This migration requires that the profile names match between the old and new releases. A mismatch has been detected and migration cannot continue until the issue is resolved. Action Create a new profile that matches the name of the source profile, and rerun migration with this matching profile as the target.
MIGR0494E: An unexpected error occured during communication with the Deployment Manager, the migration cannot continue. Resolve the error and rerun the WASPreUpgrade tool to create a new backup directory.
Explanation As part of this migration, files must be copied from the Deployment Manager to this node. These files will be stored in the backup directory. An error occured during this process that may have resulted in corruption of the backup directory. Action Investigate the original error. Common causes include network issues in communicating with the Deployment Manager, and insufficient space or permissions on the backup directory filesystem. Resolve the issue and rerun both the WASPreUpgrade and WASPostUpgrade tools because the backup directory may not be valid.
MIGR0495E: The migration function cannot use the specified backup directory, it is invalid.
Explanation The directory specified does not pass validation to be used as a migration backup directory. This may be the result of a failure during WASPreUpgrade, or corruption by a previous run of WASPostUpgrade. Action If the wrong directory was specified, rerun the tool with a valid backup directory. If the directory specified is correct, then the backup directory has been corrupted. Rerun the WASPreupgrade tools to create a new migration backup directory.
MIGR0496W: The migration of {0} terminated unexpectedly.
Explanation During the application migration process, one or more applications failed to migrate. Refer to the log files for details. Action If possible, correct the problems that are recorded in the log files. One or more applications might need to be installed manually.
MIGR0497E: The migration function cannot save files to the backup directory, it is an invalid location.
Explanation The directory specified does not pass validation to be used as a migration backup directory. Action Select an empty directory outside of any WebSphere install directories that is on a filesystem with sufficient space.
MIGR0498E: Derby database lock file detected. Cannot migrate Derby database {0} while in use.
Explanation There is a Derby database lock file detected. Cannot migrate Derby database while in use. Action Please shutdown Derby database and be sure all lock files have been removed.
MIGR0499I: Application {0} successfully deployed using the wsadmin command.
Explanation The migration function used the wsadmin command to successfully deploy the specified application. Action No user action is required.
MIGR0505E: Need adminagent information from old and new versions
Explanation While migrating an appserver that is managed by an admin agent, the path, soap port, username and password of both the old and new admin agents are required. Action Run the postupgrade command by passing in parameters for the old and new admin agents
MIGR0506E: Deregistration from old admin agent unsuccessful, make sure old admin agent process is running and the soap port is correct
Explanation When migrating an appserver that is managed by an admin agent, the appserver is first deregistered from the old admin agent. There was a failure in this deregistration process. Action Check the logs to find out why the deregistration failed. The old admin agent may not be running. Start the old admin agent and rerun the postupgrade the command.
MIGR0507E: Registration with new admin agent unsuccessful, manually register the migrated appserver to the new admin agent and job managers if applicable
Explanation When migrating an appserver that is managed by an admin agent, the appserver is registered to the new admin agent after migration completes successfully. There was a failure in this registration process. Action Check the logs to find out why registration process failed. The new admin agent may not be running. Start the new admin agent and manually register the migrated appserver if migration was successful.
MIGR0508I: Deregistering from old admin agent
Explanation Since this is a managed application server, migration will try to deregister the application server from the old admin agent first. Action Make sure that the old admin agent is running
MIGR0509I: Registering with new admin agent, make sure new admin agent process is running
Explanation Since this is a managed application server, migration will try to register the application server to the new admin agent after migration of the appserver completes successfully. Action Make sure that the new admin agent is running
MIGR0510E: Security is enabled in your managed application server. -oldAdminAgentUsername, -oldAdminAgentPassword, -newAdminAgentUsername, -newAdminAgentPassword are required arguments.
Explanation Since security is enabled on your managed application server, security credentials are needed to unregister this managed appserver from the old admin agent and register with the new admin agent Action Rerun the WASPostUpgrade command with the -oldAdminAgentUsername, -oldAdminAgentPassword, -newAdminAgentUsername, -newAdminAgentPassword parameters
MIGR0511E: Admin Agent information for the new release is invalid
Explanation The admin agent profile path for the new release is invalid Action Make sure that the admin agent information for the new release is valid
MIGR0511W: Property {0} has been mapped to conform to Microsoft SQL Server JDBC Driver requirements. Validate changes made to {1}.
Explanation Property has been converted to conform to Microsoft data source requirements. These changes should be validated for correctness on the system. Action See information center for further details.
MIGR0512E: Admin Agent information for the old release is invalid
Explanation The admin agent profile path for the old release is invalid Action Make sure that the admin agent information for the old release is correct
MIGR0512W: The following properties: {0} were used to determine the {1} setting for the Microsoft SQL Server JDBC Driver requirements. Validate changes made.
Explanation A set of properties were used to determine the final setting for a Microsoft data source property. These changes should be validated for correctness on the system. Action See information center for further details.
MIGR0513W: The Microsoft SQL Server JDBC driver property {0} was not set. Unable to determine proper value based on the value supplied by the WebSphere Connect JDBC driver property {1}.
Explanation The Microsoft Data Source property was not set because the mapping from the WebSphere Connect Data Source property or properties could not be properly determined. Action See information center for further details.
MIGR0514I: Cross machine migration detected. You will need to manually disable the {0} server on the source machine.
Explanation The WASPostUpgrade process cannot disable the source profile because it is located on a different machine. The -machineChange parameter was use by the WASPreUpgrade process to save the backup information. Action Refer to the WebSphere InfoCenter on how to manually disable the source profile.
MIGR0515W: Cannot validate if the source hostname ({0}) has the same IP address as the target hostname ({1}). Hostname changes were made to one or more of the server''s endpoints. We must validate these changes.
Explanation The migration received an UnknownHostException or a SecurityException while trying to determine the IP address of the source and/or target hostname. The migration assumed the hostname change is valid and continued. The migration updated the hostname for one or more endpoints. Action We must verify these settings. Or, to avoid this change, recreate the target profile using the hostname from the source profile and run the migration again.
MIGR0900E: The specified command is not valid.
Explanation This problem is usually caused by parameters that are misspelled or missing. Action 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: Use the -traceString parameter with the -traceFile parameter.
Explanation When you specify a file trace, also specify the level of detail to write out to trace through the -traceString parameter. Action Add the -traceString parameter. For example: -traceString "*=all=enabled" We 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. Action Supply an argument for the specified parameter.
MIGR0904W: The EAR file {0} is not valid.
Explanation The EAR file name is either not an EAR file, or the contents and structure of the EAR file do not conform to a supported Java EE, Java EE, specification. Action 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. Action Verify spelling and run the command alone, without any parameters or arguments, to get the correct syntax of the command.
MIGR0906W: We must specify the EAR file location.
Explanation No 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 Action Rerun the command with an EAR file as the first argument.
MIGR0907W: The EAR file {0} does not exist.
Explanation Cannot find the specified EAR file in the given location. Action Verify that the path is spelled correctly and that an EAR file exists in that location.
MIGR0908W: The EAR file name {0} is a directory.
Explanation The specified EAR file is a directory. Action Verify that the specified EAR file is an EAR file and not a directory.
MIGR0909W: No client JAR files are found by the name {0}.
Explanation The EAR file does not contain any client JAR files by the specified name. Action Verify that the EAR file contains the client JAR file specified.
MIGR0910W: No client JAR files are found.
Explanation The EAR file does not contain any client JAR files. Action If the specified EAR file is expected to contain client JAR files, correct the EAR file, and try the command again.