Explanation | None |
Action | No user action is required. |
Explanation | None |
Action | No user action is required. |
Explanation | The command parameters are incorrectly specified. |
Action | Verify that all of the parameters are valid and spelled correctly. |
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. |
Explanation | You 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. |
Explanation | The specified parameter is not supported by the command. |
Action | Check the spelling of the parameter and run the command again. |
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. |
Explanation | Migration support is provided for Application Server Version 5.1 and later. |
Action | If you are migrating to a supported release, verify that the directory name is correct and rerun the 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. |
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. |
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. |
Explanation | The system is unable to create a directory with the name that you 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: http://www.ibm.com/software/webservers/appserv/was/support/ or consult the appropriate operating system documentation. |
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: http://www.ibm.com/software/webservers/appserv/was/support/ |
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: http://www.ibm.com/software/webservers/appserv/was/support/ |
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. |
Explanation | An error occurred while reading the XML file to import during migration. |
Action | Rerun the command with a valid XML import file. |
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. |
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. |
Explanation | An attempt to read the specified file failed. |
Action | Verify that the file exists, and rerun the command. |
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. |
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. |
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. |
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. |
Explanation | The directory was created during normal processing. |
Action | No user action is required. |
Explanation | The function is copying a directory and its contents. |
Action | No user action is required. |
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. |
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. |
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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |
Explanation | The specified object is being added to the configuration of the new Application Server version. |
Action | No user action is required. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The configuration file was successfully read. |
Action | No user action is required. |
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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | No Samples are migrated by the WASPostUpgrade command. |
Action | No user action is required. |
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. |
Explanation | The backup directory that was specified on the command line does not exist. |
Action | Rerun the command with a valid backup directory that was created by the WASPreUpgrade command. |
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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration has completed with no warning or error messages. |
Action | No user action is required. |
Explanation | The migration completed with some warning messages, but no errors occurred. |
Action | 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. |
Explanation | The migration command failed. |
Action | 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. |
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. |
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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified backup directory is created from an unsupported version of Application Server. |
Action | Rerun the migration command with a valid backup directory that was created by the WASPreUpgrade command. |
Explanation | An unexpected error occurred. |
Action | If the problem persists, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration failed to complete because errors occurred during migration. |
Action | 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. |
Explanation | The specified configuration file, which did not exist in the new Application Server configuration, is successfully created. |
Action | No user action is required. |
Explanation | The specified configuration file is ready to be saved. |
Action | No user action is required. |
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. |
Explanation | The required steps that save the existing configuration information have started. |
Action | No user action is required. |
Explanation | The files that you need to restore your configuration on the new release are being copied to the backup directory. |
Action | No user action is required. |
Explanation | The process of backing up your previous configuration is complete. |
Action | No user action is required. |
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. |
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. |
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. |
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. |
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 | 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. |
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: http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |
Explanation | The attributes of the specified authentication mechanism are being updated. |
Action | No user action is required. |
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. |
Explanation | The migration function used the wsadmin command to deploy the specified application. |
Action | No user action is required. |
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. |
Explanation | The specified value application installation directory has been updated to use the common WebSphere variables |
Action | No action is required, |
Explanation | Automated migration for the file is starting. |
Action | No user action is required. |
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. |
Explanation | No administrative applications are migrated during the WASPostUpgrade process. |
Action | No user action is required. |
Explanation | Another Application Server process has a lock on the configuration directory. |
Action | Close any running Application Server processes, and run migration again. |
Explanation | The deployment manager might not have been running during migration. |
Action | 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. |
Explanation | The function is trying to connect to the deployment manager using the specified protocol. |
Action | No user action is required. |
Explanation | The configuration is successfully synchronized. |
Action | No user action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The existing configuration is saved in the <samp>temp</samp> directory. |
Action | No user action is required. |
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. |
Explanation | Leftover grants that are found in the old file are not found in the new file. |
Action | No user action is required. |
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. |
Action | Uninstall and reinstall 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. |
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 Application Server 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. |
Action | If you want to roll back to use the previous Application Server Version 5.1, 6.0 or 6.1 environment instead of Version 7.0, you must re-enable that configuration. To do this, go to the /bin directory of the previous Version 5.1 6.0 or 6.1 installation and run the migrationDisablementReversal.jacl script. |
Explanation | During a federated migration, a JMX connection must be established with the deployment manager. 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 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 Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The series of steps needed to save the existing configuration information for the profile is starting. |
Action | No user action is required. |
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. |
Explanation | The profile did not exist in the previously installed WebSphere. |
Action | Rerun the command with the correct profile name. |
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. |
Explanation | A default profile does not exist and the -oldProfile parameter was not specified. |
Action | Rerun the command with the correct profile name. |
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. |
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. |
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. |
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. |
Explanation | The application cannot be installed because the required supporting software is not available. |
Action | No user action is required. |
Explanation | All servers must belong to a core group. This server is added to the default core group. |
Action | No user action is required. |
Explanation | Transports are migrating to corresponding channels in the new release. |
Action | No user action is required. |
Explanation | Each transport is migrated to a new channel and belongs to a new default thread pool. |
Action | No user action is required. |
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 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. |
Action | If you want to roll back to use the previous Application Server Version 5.1, 6.0 or 6.1 environment instead of Version 7.0, you must re-enable that configuration. To do this go to the /bin directory of the previous Version 5.1, 6.0 or 6.1 installation and run the migrationDisablementReversal.jacl script. |
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. |
Explanation | The parameter was specified when running the command. The value that is specified cannot be found in the profile. |
Action | Run the command again with a correct value for the parameter. |
Explanation | The configuration is saved. |
Action | No user action is required. |
Explanation | A default profile does not exist and the correct profile parameter was not specified. |
Action | Rerun the command with the correct profile name. |
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. |
Explanation | While processing a deployment manager 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. |
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. |
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. |
Action | Perform migration again using a profile name with the matching cell name. |
Explanation | All nodes must belong to a node group. This node is added to the default node group. |
Action | No user action is required. |
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. |
Action | When the application is used for Application Server Version 6.x profiles only, use the administrative console to modify this attribute. |
Explanation | The migration completed with no warning or error messages. |
Action | No user action is required. |
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. |
Explanation | Certain files in the Application Server Version 5 or 6 environment might be modified during the migration of a version 7 deployment manager that manages version 5 or 6 nodes. By running the backupConfig command against your version 5 or 6 environment, you provide 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 deployment manager. |
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. |
Explanation | This release of Application Server cannot manage nodes prior to Version 6.0.2.0 without a fix. |
Action | Install the required fix to Version 6.0.0.x and 6.0.1.y nodes prior to migration. |
Explanation | The deployment manager to which this node belongs is not the deployment manager currently running. |
Action | Shut down the incorrect deployment manager, and start the deployment manager that is currently managing the node to be migrated. |
Explanation | The migration of Cloudscape to Derby was successfully for this particular database. |
Action | No user action is required. |
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. |
Explanation | This error occurs if the new deployment manager 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. |
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. |
Explanation | This error occurs when -keepAppDirectory true and -appInstallDirectory are both specified. |
Action | Select only one of the two parameters, or specify -keepAppDirectory false. |
Explanation | Applications that are already installed in the new profile will not be migrated. |
Action | No user action is required. |
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. |
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. |
Explanation | To avoid having two deployment managers managing the same cell, you must shut down the current version of deployment manager when specifying -keepDMgrEnabled=true |
Action | Shut down the current version of deployment manager, and perform the migration again. |
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. |
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. |
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. |
Explanation | The specified object is being copied to the configuration of the new Application Server version. |
Action | No user action is required. |
Explanation | The node or server name specified does not exist. |
Action | Run the command again and specify existing node and server names. |
Explanation | During a managed node migration, any new Version 7 configuration changes that existed prior to running WASPostUpgrade might need to be reapplied after the WASPostUpgrade process completes. |
Action | Reapply preexisting Version 7 cell level changes after the managed node migration has been completed. |
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, it is recommended that it be deleted, unless you have previously configured data sources that still use it. |
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. You can update the port settings using the administrative console or the wsadmin scripting interface as required by your environment. |
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 your environment to resolve port conflicts. Use the Application Server administrative interfaces or the wsadmin scripting interface to update these values. |
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. |
Explanation | Migration copied the file because it had not already been processed during migration. |
Action | No user action is required. |
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. |
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. |
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. |
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. |
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 Application Server configuration. Stop the deployment manager of the existing configuration before starting the deployment manager in the new configuration. Use the deployment manager of the new configuration to manage the environment. |
Action | If you want to use the old environment, restart the prior version Deployment Manager. |
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 deployment manager in the new configuration. The deployment manager of the new configuration must be used to manage the environment. |
Action | If you want to use the old environment you will need to restart the prior version of the Deployment Manager and Managed node. |
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. |
Explanation | This indicates that a specific backup of Application Server files are being migrated into this configuration. |
Action | No user action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | Property has been modified to conform to Microsoft data source requirements. These changes should be validated for correctness on your system. |
Action | See information center for further details. |
Explanation | Performing conversion on WebSphere Applilcation Server DataDirect resource. |
Action | None |
Explanation | Performing conversion on WebSphere Applilcation Server DataDirect resource. |
Action | None |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | WASPreUpgrade requires that the <backupDirectoryName> and <currentWebSphereDirectory> be specified. |
Action | Run WASPreUpgrade again supplying the required parameters. |
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. |
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. |
Explanation | Performance may degrade with coregroups of large size. |
Action | Redistribute coregroup processes to smaller coregroup groupings. |
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. |
Explanation | The identified parameter is not needed for the current migration. |
Action | No action is neccessary. |
Explanation | While migrating a deployment manager node, the node names of the deployment manager in the new configuration must either be unique from all nodes in the old configuration or be identical to the deployment manager node name in the old release. |
Action | Create a new deployment manager profile in the new configuration where the node name for the deployment manager matches the node name from the old configuration. |
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. |
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 your system you may change the value. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The migration function used the wsadmin command to successfully deploy the specified application. |
Action | No user action is required. |
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 |
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. |
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. |
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 |
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 |
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 |
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 |
Explanation | Property has been converted to conform to Microsoft data source requirements. These changes should be validated for correctness on your system. |
Action | See information center for further details. |
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 |
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 your system. |
Action | See information center for further details. |
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. |
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. |
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 | You 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. |
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. |
Explanation | When you specify a file trace, you must 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" You must include the quotation marks. |
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. |
Explanation | The enterprise archive (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 Platform Enterprise Edition, Java EE, specification. |
Action | Verify that the path is spelled correctly and that a valid EAR file is in that location. |
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. |
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 |
Action | Rerun the command with an EAR file as the first argument. |
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. |
Explanation | The specified enterprise archive (EAR) file is a directory. |
Action | Verify that the specified EAR file is an EAR file and not a directory. |
Explanation | The enterprise archive (EAR) file does not contain any client Java archive (JAR) files by the specified name. |
Action | Verify that the EAR file contains the client JAR file that is specified. |
Explanation | The enterprise archive (EAR) file does not contain any client JAR files. |
Action | If the specified EAR file is expected to contain client Java archive (JAR) files, correct the EAR file, and try the command again. |