MIGR

MIGR0001I: The class name of the WASPreUpgrade command is WASPreUpgrade
MIGR0002I: The class name of the WASPostUpgrade command is WASPostUpgrade
MIGR0102E: An unsupported command line parameter was used.
MIGR0103E: You must specify the backup directory name.
MIGR0104E: You must specify the currently installed Application Server directory name.
MIGR0106E: The illegal argument {0} is specified.
MIGR0107E: An incorrect format for an optional parameter is specified.
MIGR0108E: The directory {0} does not contain a WebSphere version that can be upgraded.
MIGR0110E: The currently installed version of Application Server is not supported by this command.
MIGR0111E: The migration function cannot use the specified backup directory because it is a file.
MIGR0112E: The specified backup directory cannot be used because it is not writable.
MIGR0113E: The specified backup directory cannot be used because it cannot be created.
MIGR0114E: The migration function cannot find the setupCmdLine setting {0}.
MIGR0115E: The migration function cannot run program: {0}.
MIGR0117E: The specified Application Server directory does not contain a valid product file {0}.
MIGR0121E: The migration function cannot read the import XML document {0}, exception {1}.
MIGR0122E: The migration function cannot read configuration file {0}.
MIGR0123E: The migration function cannot import object {0} of type {1}, exception {2}.
MIGR0124E: The migration function cannot import XML data file {0}.
MIGR0201I: The migration function initialized log file {0}.
MIGR0202W: The migration function is unable to initialize log file {0}.
MIGR0206W: The migration function cannot copy the directory. The source file {0} does not exist.
MIGR0207W: The migration function cannot copy the directory {0}.
MIGR0210I: The migration function is creating a directory {0}.
MIGR0211I: The migration function is copying a directory {0}.
MIGR0212E: The migration function cannot create the directory {0}. A file with this name already exists.
MIGR0213E: The migration function cannot create a directory {0}.
MIGR0214W: The migration function cannot copy the file. Source {0} does not exist.
MIGR0215W: The migration function cannot copy the file and open the destination file {0}.
MIGR0216W: The migration function cannot copy the file and transfer from source {0} to destination {1}.
MIGR0217W: The migration function cannot close file {0}.
MIGR0221I: The migration function is reading the previously saved configuration file {0}.
MIGR0223I: The migration function is adding {0} entry {1} to the model.
MIGR0227W: The migration function cannot make a backup copy of configuration file {0}; exception {1} occurred.
MIGR0228E: The migration function cannot save configuration files; exception {0} occurred.
MIGR0229I: The migration function is updating the attributes of {0} entry {1}. This entry is already defined in the existing model.
MIGR0234W: The migration function cannot locate object {0} of type {1}.
MIGR0237I: The migration function read configuration file {0} successfully.
MIGR0241I: Output of {0}.
MIGR0249E: An error occurred while updating the <samp>plugin-cfg.xml</samp> file; exception {0} was caught. Run the GenPlugIncfg command manually.
MIGR0251I: The migration does not include object {0} of type {1}; it is a Sample.
MIGR0252W: The migration function cannot restore configuration file {0}. An exception {1} occurred.
MIGR0253E: The backup directory {0} does not exist.
MIGR0255E: The migration function found an unacceptable substitution value {0}.
MIGR0257E: The environment variable {0} was not set.
MIGR0259I: The migration has successfully completed.
MIGR0271W: Migration completed successfully, with one or more warnings.
MIGR0272E: The migration function cannot complete the command.
MIGR0280W: Application {0} is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0281W: All CORBA servers are disabled because the corresponding IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0283E: The migration function cannot read backup options file {0}, exception {1}.
MIGR0284E: The version of WebSphere {0} in the specified backup directory cannot be migrated to profile {1}.
MIGR0285E: An unexpected internal error occurred with exception {0}.
MIGR0286E: The migration failed to complete.
MIGR0287I: The migration function successfully created configuration file {0}.
MIGR0288I: Configuration file {0} ready to be saved.
MIGR0289E: The entry {0} in entry {1} does not exist.
MIGR0300I: The migration function is starting to save the existing Application Server environment.
MIGR0302I: The existing files are being saved.
MIGR0303I: The existing Application Server environment is saved.
MIGR0304I: The previous WebSphere environment is being merged into this profile.
MIGR0307I: The restoration of the previous Application Server environment is complete.
MIGR0310E: A value that is specified for {0} is not valid: {1}.
MIGR0313E: More than one {0} directory exists; specify a directory using the {1} parameter.
MIGR0319E: This node is already federated into a cell manager configuration.
MIGR0327E: A failure occurred with {0}.
MIGR0331W: Port {0} in file {1} is migrated, but is already assigned in file {2}; this situation might result in port conflicts.
MIGR0332I: The attributes of the {0} authentication mechanism are updating.
MIGR0335I: Attributes of the {0} user registry are updating to reflect the information for server ID {1}.
MIGR0339I: Application {0} is deploying using the wsadmin command.
MIGR0340W: Application {0} did not deploy.
MIGR0341W: Application installation directory has been updated to {0}.
MIGR0344I: Processing configuration file {0}.
MIGR0345E: The migration backup directory is not compatible with this Application Server version.
MIGR0346I: Object {0} of type {1} is not migrating; it is an administrative application.
MIGR0349E: The migration function cannot access the configuration directory.
MIGR0350W: Synchronization with the deployment manager using the {0} protocol failed.
MIGR0351I: The migration function is attempting to synchronize with the deployment manager using the {0} protocol.
MIGR0352I: The synchronization with the deployment manager is successful.
MIGR0353E: The migration function cannot create configuration file {0}.
MIGR0357W: The extended messaging service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0360W: The staff service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0363W: The IBM WebSphere Business Integration adapter service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0365W: The member manager service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0366W: The business process container is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0367I: Backing up the current Application Server environment.
MIGR0371I: The name-value pairs that existed in the old file are not found in the new file.
MIGR0372I: Migrated grant permissions follow.
MIGR0378E: The node name of the new configuration must be the same as the old configuration: {0} for this environment.
MIGR0379W: Do not use the existing deployment manager in the old configuration. It has been disabled.
MIGR0380E: The JMX connection is not established with the deployment manager node {0}, using connector type of {1} on port {2}. The WASPostMigration program is now closing. No changes are made to the local Application Server environment.
MIGR0385I: Starting to save profile {0}.
MIGR0386E: Profile {0} is not found in the currently installed Application Server.
MIGR0387E: The backup directory does not contain profile {0}.
MIGR0389I: Applications will not be migrated, the -includeApps attribute was set to false.
MIGR0390E: The backup directory does not contain a default profile.
MIGR0394W: IBM WebSphere Web Service Reference service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0395W: IBM WebSphere Application Event service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0396W: IBM WebSphere Business Context Data service is disabled because the required IBM WebSphere Business Integration Server Foundation feature is not installed.
MIGR0397W: Service Integration Bus migration failed.
MIGR0398E: An unsupported IBM WebSphere Business Integration Server Foundation resource is found in an application.
MIGR0400I: Server {0} is added to the default core group.
MIGR0402I: Existing transports are migrating into the transport channel service; see the information center for further information.
MIGR0403I: The transport with a port address of {0} is migrating to channel {1} and belongs to the {2} ThreadPool.
MIGR0404W: Do not use the node agent in the old configuration. It has been disabled.
MIGR0406E: The -nodeName parameter must also be provided if the -serverName parameter is provided for this profile type.
MIGR0407E: The {0} parameter {1} cannot be found in the profile.
MIGR0408I: The configuration is saved successfully.
MIGR0409E: The currently installed WebSphere does not contain a default profile.
MIGR0410W: Unable to add server {0} to the default coregroup
MIGR0412W: Node name {0} already exists in the configuration at the current Application Server version level. It will not be updated.
MIGR0413W: Node name {0} does not exist in the configuration at the current Application Server version level. It will not be updated.
MIGR0415E: The cell name {0} from the old configuration does not match the cell name {1} in the target profile. No migration can occur.
MIGR0417I: Node {0} is added to the default node group.
MIGR0419I: The -useMetaDataFromBinary attribute is set to false for application {0}. The local changes are added to the repository.
MIGR0420I: The first step of migration completed successfully.
MIGR0421W: The first step of migration completed with warnings.
MIGR0425I: A deployment manager migration is detected. Before continuing with the WASPostUpgrade process, run the backupConfig command on your federated nodes.
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.
MIGR0427W: Node {0} has been migrated, but may not be manageable in current release.
MIGR0428E: Incorrect Deployment Manager connection established.
MIGR0429I: Cloudscape Database {0} was successfully migrated. See log {1}
MIGR0430W: Cloudscape Database {0} failed to migrate to {1} Database. See log {2}
MIGR0431E: Federated node {0} already exists in current configuration. Migration cannot continue.
MIGR0432W: Found server {0} to be of type {1} which is unsupported in current product version. {0} will not be migrated.
MIGR0433E: Conflicting parameters, -keepAppDirectory true and -appInstallDirectory, have both been specified. If -appInstallDirectory is specified, -keepAppDirectory must be false.
MIGR0434I: Will not be migrating object {0} of type {1}, it is already installed.
MIGR0435W: Could not resolve variable {0}.
MIGR0436W: Could not process resource {0} due to variable issues.
MIGR0437E: Detected current version of deployment manager running while -keepDMgrEnabled attribute set.
MIGR0438W: Not copying file or directory {0} because a version of the file or directory already exists in current version.
MIGR0439E: Can not initialize trace services.
MIGR0440W: The migration of one or more applications terminated unexpectedly.
MIGR0441I: The migration function is copying {0} entry {1} to the model.
MIGR0443E: {0} {1} does not exist, will not continue.
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.
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.
MIGR0446I: Port conflicts were resolved during migration as shown below for document: {0}
MIGR0449I: The following ports were not changed as part of migration because no migrated servers contained these values.
MIGR0450W: Some files were copied directly without being processed by migration, review MIGR0451W messages in the log file.
MIGR0451W: Migration copied file originally located at {0} to local path {1}
MIGR0452W: Migration could not locate a file matching {0} when migrating {1}. The reference has not been modified.
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.
MIGR0454I: The {0} setting in file {1} is deprecated.
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.
MIGR0456W: Do not use the existing deployment manager in the old configuration.
MIGR0457W: Do not use the node agent in the old configuration.
MIGR0458E: Security is enabled in your prior configuration. -username and -password are required arguments.
MIGR0459I: Application Server configuration files are being migration.
MIGR0460E: Application Server migration is not supported in this configuration.
MIGR0461I: Application Server has already been migrated.
MIGR0462I: Application Server factor is saving base configuration files.
MIGR0463I: Nothing to migrate at this time. The current profile has already been migrated with all information from enabled features.
MIGR0464E: Failed to stop prior release nodeagent.
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.
MIGR0466E: No value was found for the argument {0}. This argument requires a value{1}.
MIGR0467W: A user defined data source helper {0} has been detected. It will be migrated, but it must be reimplemented to work correctly.
MIGR0468W: Adding properties unique to the Microsoft SQL Server JDBC Driver. Review the default values to ensure the desired behavior.
MIGR0469W: Removing properties unique to the WebSphere Connect JDBC driver. These features are no longer available:
MIGR0471W: Property {0} has been modified or replaced to conform to Microsoft SQL Server JDBC Driver requirements. Validate changes made.
MIGR0472I: Converting WebSphere Connect JDBC Provider "{0}" to {1} Provider.
MIGR0473I: Converting WebSphere Connect JDBC driver data source "{0}" to {1} data source.
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.
MIGR0476E: This command is required to be run against the Deployment Manager's configuration and the changes manually sychronize to the Managed nodes.
MIGR0477I: The Deployment Manager's configuration has been updated. A synchronization with the effected Managed nodes must occur before using these updated settings.
MIGR0478E: The port value for the endpoint {0} in of the server {1} is invalid or missing.
MIGR0479E: The host value for the endpoint {0} in of the server {1} is invalid or missing.
MIGR0480E: The node {0} specified for the -nodeName parameter is not at the current release. Migrate node to current release and run tool again.
MIGR0481E: The {0} {1} specified for the {2} parameter does not exist.
MIGR0482E: You must specify the <backupDirectoryName> and <currentWebSphereDirectory>.
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.
MIGR0484E: No profiles or instances found with name {0}.
MIGR0485W: Process count exceeds the maximum recommended limit of {0} processes per coregroup.
MIGR0486I: The {0} setting in file {1} is deprecated.
MIGR0487I: The {0} parameter not required in this scenario, and is being ignored.
MIGR0488E: The deployment manager node name in the new configuration ({0}) cannot be the same as a nodeagent node in the old configuration.
MIGR0489E: The migration backup directory profile is of type {0} which is not compatible with this profile type {1}.
MIGR0490I: Changing the {0} setting from {1} to {2} in the file {3} to meet performance requirements.
MIGR0491W: The migration function cannot continue because there are too many open files.
MIGR0492W: The SOAP port has changed from {0} to {1}, you must manually synchronize the managed nodes with the Deployment Manager.
MIGR0493E: The profile name {0} does not match the target profile {1}, the profile names must match for this migration.
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.
MIGR0495E: The migration function cannot use the specified backup directory, it is invalid.
MIGR0496W: The migration of {0} terminated unexpectedly.
MIGR0497E: The migration function cannot save files to the backup directory, it is an invalid location.
MIGR0498E: Derby database lock file detected. Cannot migrate Derby database {0} while in use.
MIGR0499I: Application {0} successfully deployed using the wsadmin command.
MIGR0505E: Need adminagent information from old and new versions
MIGR0506E: Deregistration from old admin agent unsuccessful, make sure old admin agent process is running and the soap port is correct
MIGR0507E: Registration with new admin agent unsuccessful, manually register the migrated appserver to the new admin agent and job managers if applicable
MIGR0508I: Deregistering from old admin agent
MIGR0509I: Registering with new admin agent, make sure new admin agent process is running
MIGR0510E: Security is enabled in your managed application server. -oldAdminAgentUsername, -oldAdminAgentPassword, -newAdminAgentUsername, -newAdminAgentPassword are required arguments.
MIGR0511E: Admin Agent information for the new release is invalid
MIGR0511W: Property {0} has been mapped to conform to Microsoft SQL Server JDBC Driver requirements. Validate changes made to {1}.
MIGR0512E: Admin Agent information for the old release is invalid
MIGR0512W: The following properties: {0} were used to determine the {1} setting for the Microsoft SQL Server JDBC Driver requirements. Validate changes made.
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}.
MIGR0514I: Cross machine migration detected. You will need to manually disable the {0} server on the source machine.
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. You must validate these changes.
MIGR0900E: The specified command is not valid.
MIGR0901W: You must use the -traceString parameter with the -traceFile parameter.
MIGR0903W: A value for attribute {0} is missing.
MIGR0904W: The enterprise archive (EAR) file {0} is not valid.
MIGR0905W: An unacceptable parameter was specified {0}.
MIGR0906W: You must specify the enterprise archive (EAR) file location.
MIGR0907W: The enterprise archive (EAR) file {0} does not exist.
MIGR0908W: The enterprise archive (EAR) file name {0} is a directory.
MIGR0909W: No client Java archive (JAR) files are found by the name {0}.
MIGR0910W: No client Java archive (JAR) files are found.


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.websphere.migration.WASUpgrade.dita
File name: com.ibm.websphere.migration.WASUpgrade.html