Explanation | The configuration data might be removed or the ID of the configuration is not valid. |
Action | Issue a query command to confirm that this configuration data still exists. |
Explanation | The specified document is not found. It might be removed already, or the document URI is not valid. |
Action | Issue a query command again to make sure that the document URI is the same as the returned query command. |
Explanation | Either the document cannot be retrieved from the configuration repository, or the document is not a valid XMI document. See the nested exception for details. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An inconsistency exists in the document content, or the document cannot be saved in the configuration repository successfully. See the nested exception for details. |
Action | Discard the change and repeat the operation. |
Explanation | The identified attribute name is not valid. |
Action | Get the meta information for the object and verify that the spelling of the attribute name is correct. Note that attribute names are case sensitive. |
Explanation | The identified attribute name path is not valid. |
Action | Get the meta information for the object and verify that the spelling of the attribute name is correct. Note that attribute names are case sensitive. |
Explanation | The identified type is not valid. |
Action | Get the supported data type list and verify the data type name. Note that data type names are case sensitive. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The type of the supplied attribute value does not match the attribute type. |
Action | Get the meta information for that attribute and verify that the types match. |
Explanation | The type of the supplied attribute value does not match the attribute type. |
Action | Get the meta information for that attribute and verify that the types match. |
Explanation | You cannot modify the identified attribute. |
Action | Do not attempt to modify a read-only attribute, or change attribute permissions. |
Explanation | The attribute path cannot be modified. |
Action | Do not attempt to modify a read-only attribute path, or change attribute path permissions. |
Explanation | An exception occurred while obtaining a validation manager for the session. |
Action | See the nested exception for information. |
Explanation | The validate operation failed for the specified session and specified scope. |
Action | See the nested exception for more details. |
Explanation | The node attribute value of the WASQueue instance is not valid. |
Action | Supply a valid node name as the attribute value for the node attribute on the WASQueue object. |
Explanation | More than one JMS server value is defined on the specified node. |
Action | Modify the configuration to remove the invalid JMS server value. |
Explanation | A required attribute is not provided. |
Action | Supply the required attribute. |
Explanation | The template type is different from the object type being created. |
Action | Check the input parameters and verify that the template and object types match. |
Explanation | The serverindex.xml document is not available for update. Some inconsistencies might exist between the serverindex.xml document and the rest of the configuration. |
Action | Manually update the serverindex.xml document to keep it consistent with the configuration. |
Explanation | The operation is not supported. |
Action | Use the AddNode command-line utility to incorporate a node into a cell. |
Explanation | The supplied parameter does not follow the detailed syntax described in the API documentation. |
Action | Refer to the ConfigService#resolve method document for the syntax of a containment path. |
Explanation | The server was created successfully, but the SERVER_LOG_ROOT variable map creation under the newly created server scope failed. |
Action | Manually define the VariableMap SERVER_LOG_ROOT value as ${LOG_ROOT}/serverName under the server scope in the variables.xml file. |
Explanation | When a new cluster member is added to a server cluster, the applications that are deployed on the clusters are automatically deployed on the new cluster member. In this case, the definition of an existing cluster member cannot be found, so the application deployment information cannot be updated correctly for the new cluster member. |
Action | Check the server cluster configuration for inconsistencies or errors. |
Explanation | An inconsistency exists between the server configuration and its serverindex.xml document. |
Action | Manually edit the server index document to keep it consistent with the server configuration. |
Explanation | The cluster member is removed from a server cluster, but the server definition of the cluster member cannot be removed. |
Action | Manually remove the server definition from the cluster configuration. |
Explanation | A server can not be converted to a server cluster if it is part of an existing cluster. |
Action | No user action is required. |
Explanation | If a user ID is specified, a password must be specified when the defaultPrincipalMapping value is defined. |
Action | Supply a password for the specified user ID. |
Explanation | If the user ID and password pair is not supplied in a defaultPrincipalMapping for a J2CConnectionFactory, use of an existing JAASAuthData entry is assumed. |
Action | Supply a user ID and password pair, or use an alias matching an existing JAASAuthData entry. |
Explanation | If a user ID and password are specified, a JAASAuthData entry is automatically created when a defaultPrincipalMapping value is defined. The creation of a JAASAuthData entry failed because an alias with the specified name already exists. |
Action | Omit the user ID and password to use an existing JAASAuthData entry, or use a different alias to create a new JAASAuthData entry. |
Explanation | If a server is deleted before the installed applications are uninstalled, those applications fall into an inconsistent state and might not run normally. |
Action | Uninstall the applications on the server before deleting the server. |
Explanation | The input parameter value is not a valid node name. Note that node names are case sensitive. |
Action | Correct the input value. |
Explanation | The administrator role is required to modify the specified attribute. |
Action | Log in as a user who has an administrator role and try the command again. |
Explanation | This operation is not supported when the wsadmin tool or the configuration service runs in local mode without connecting to the server. |
Action | Start the server and repeat the command in remote mode. |
Explanation | Certain types of configuration objects require that one of their attributes has a unique value. For example, the value of the name attribute of the VirtualHost configuration object must be unique. |
Action | Specify a different attribute value to satisfy the uniqueness requirement. |
Explanation | This J2CResourceAdapter object is defined in the resources.xml file of an administrative layer higher than the specified layer. Consequently, removal of the object at the specified level destroys consistency across the entire defined administrative area. |
Action | Uninstall the J2CResourceAdapter from the higher administrative layer to maintain consistency across the entire administrative area. |
Explanation | An unexpected error occurred while retrieving the specified attribute of the specified J2CResourceAdapter object. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The $AdminConfig uninstallJ2CResourceAdapter command accepts the node level J2CResourceAdapter MBean only. |
Action | Specify the node level J2CResourceAdapter MBean for the $AdminConfig uninstallResourceAdapter command. Remove the cell level or server level J2CResourceAdapter with the $AdminConfig remove command. |
Explanation | This J2CResourceAdapter object is defined in the resources.xml file of an administrative layer higher than the specified layer. Consequently, removal of the object at the specified level destroys consistency across the entire defined administrative area. |
Action | Uninstall the J2CResourceAdapter from the higher administrative layer to maintain consistency across the entire administrative area. |
Explanation | renameCell command can not be run when administrative client is connected to a running server. This command changes the cell name and hence needs to be run when server is shut down. |
Action | Stop the server by running stopServer or stopManager script before running this command. |
Explanation | The cell name cannot have leading or trailing spaces and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ' [ ] |
Action | Specify a different cell name that complies with cell name rules. |
Explanation | The system continues to create the new server. While creating the server, the server cannot be added to the specfied core group. |
Action | Check the configuration to determine if the core group exists. |
Explanation | The specified core group cannot be found. The system continues with the configuration operation. |
Action | Check the configuration to determine if the core group exists. |
Explanation | The node cannot be found in the configuration on this server. The system continues the configuration operation. |
Action | Check the configuration to determine if a node might be inadvertently deleted. |
Explanation | While deleting the specified server, the system attempted to remove the server from its core group, but an exception occurred. The system continues the operation to delete the server. |
Action | Evaluate the exception to determine the cause of the problem. Check the configuration to determine if a core group is inadvertently deleted. |
Explanation | The system could not find the core group while performing a delete operation. The system continued the delete operation. |
Action | Check the configuration to determine if a core group was inadvertently deleted. |
Explanation | The cluster member can be identified either by specifying the member object ID, or by specifying the member name, node name and cluster name. |
Action | Specify a cluster object ID for the command target object without specifying the clusterName, memberNode, and memberName parameters. Alternatively, specify all three of these parameters without specifying the target object ID. |
Explanation | The given ConfigService attribute is valid starting at the specified version. |
Action | No user action is required. |
Explanation | The given ConfigService attribute was deprecated at the given version. This attribute is valid, but may not be in the future. |
Action | No user action is required. |
Explanation | The given ConfigService attribute has been removed at this version. This attribute is not valid at the given version. |
Action | Use a valid ConfigService attribute. See the API documentation for valid attributes. |
Explanation | The MBean request to install the resource adapter failed. Ensure that the version of the target node matches the version of the resource adapter. |
Action | Ensure that the version of the target node matches the version of the resource adapter. A V1.5 Resource Adapter Archive (RAR) file cannot be installed on WebSphere Application Server V5 or earlier. |
Explanation | If any J2C Resource Adapter exist to shared the same archive path, isolated Class Loader value should be consistent. |
Action | The inconsistent J2C Resource Adapter can not exist. Delete the old J2C Resource Adapter with different isolatedClassLoader value or create the new one to have the same value. |
Explanation | J2C Resource Adapter can not be created with IsolatedClassLoader value true, if nativePath is not null. |
Action | Do not specify nativapath or set IsolatedClassLoader false. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified node cannot be a member of the specified node group because the node group is a node group on the distributed platform. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node group is a sysplex node group in a different sysplex. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node does not belong to any node groups. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node does not belong to any node groups. |
Action | Choose another node or add the node to the node group and try the operation again. |
Explanation | A node cannot be removed from a node group because it contains cluster members in that node group. |
Action | Add the node that has cluster members to another node group before removing that node from the original node group. |
Explanation | A node cannot be removed from a node group. A node must always be a member of at least one node group. |
Action | Ensure that the node group contains at least one member. |
Explanation | The specified node group cannot be found in the configuration repository. |
Action | Determine if the specified node group exists, and if the correct node group name is specified. Specify a valid node group name and try the operation again. |
Explanation | The node member cannot be added to the node group because a member with that name already exists in the node group. |
Action | Determine if the specified node is already in the node group, or if the correct node name is specified. Specify a valid node name and try the operation again. |
Explanation | The specified node is not eligible to be a member of the specified node group because the node group is a sysplex node group, which is unique to the z/OS operating system. |
Action | Choose another node or node group and retry the operation. |
Explanation | A node group cannot be removed if it contains members. |
Action | Remove the node group members first and try the operation again. |
Explanation | The default node group cannot be deleted because a default node group is required for node group administration. |
Action | Do not attempt to delete the default node group. |
Explanation | A node group property with the specified name already exists. |
Action | Choose another name for the node group property, and try the operation again. |
Explanation | Nodes that belong to a sysplex node group must remain in a sysplex node group because sysplex node group membership is required. |
Action | Use the addNodeGroupMember command to move a node to a different sysplex node group. |
Explanation | The short name must be unique within the same sysplex. |
Action | Verify that the short name is unique within the same sysplex. |
Explanation | The node is not eligible to be a member of the sysplex node group because Version 5 z/OS nodes can be a member of the default sysplex node group only. |
Action | Do not attempt to add Version 5 nodes on the z/OS platform to a sysplex node group. |
Explanation | The specified node group is not a sysplex node group. |
Action | Choose another node or node group and retry the operation. |
Explanation | The unmanaged node cannot be added to the node group because a node group must contain managed nodes only. |
Action | Determine if the specified node is a managed node or if the correct node name was specified. Choose a managed node and retry the operation. |
Explanation | The specified node group already exits in the configuration repository. |
Action | Specify a different node group name and try the operation again. |
Explanation | Cluster scope resource or variable configurations are introduced at Version 6. |
Action | Configure the resource or variable at the server or node scope to achieve the same effect. |
Explanation | Application scope resource or variable configurations are introduced at Version 6. |
Action | Configure the resource or variable at the server or node scope to achieve the same effect. |
Explanation | A VariableMap object already exists under the specified scope. Only one VariableMap object can exist under a specific scope. |
Action | Do not attempt to create more than one VariableMap object per scope. Configure variables under just one VariableMap object for each scope. |
Explanation | The cluster member could not be created for the cluster because no cluster member exists at the product version specified for the new cluster member. |
Action | Create a new cluster member at the same product version as an existing member of the cluster. For example, migrate one of the nodes of an existing cluster member to the same product version as the cluster member you are attempting to create for the cluster. The version of the cluster member changes when you migrate its node to the new version. Then create the new cluster member. |
Explanation | A server template cannot be created using a server on the specified node because the operating system is not specified for the node. The node might be a version 5 node in a mixed cell environment, and might not have been started. |
Action | Start the node agent for the specified node. Ensure that the deployment manager is running. Then create the server template by using a server in the specified node. |
Explanation | The current user does not have access to perform the intended operation on the specified configuration data. |
Action | Login as a different user who has access to this config data. |
Explanation | The configuration changes that were attempted exceed the license restrictions, for example, the maximum number of clusters, or members in a cluster. |
Action | Make configuration changes within the license restrictions. |
Explanation | The license restrictions could not be verified for the attempted configuration change. The license restriction data might be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The template used has been deprecated, which still works, but some time in the future, it will no longer be available. |
Action | Begin using the new template replacement as soon as possible. |
Explanation | A cluster with the specified name is already configured. |
Action | Choose another name for the cluster, and retry the operation. |
Explanation | A replication domain with the name of the specified cluster is already configured. |
Action | If the named replication domain is no longer needed, delete it from the configuration. Otherwise, choose another name for the cluster. Then retry the operation. |
Explanation | A server with the specified name is not configured on the specified node. |
Action | Determine if the names of the server and node are correct. Specify the correct server and node names for a configured server. Then retry the operation. |
Explanation | The server is already a member of the specified cluster. It cannot be a member of another cluster. |
Action | Choose another server to include in the cluster, or do not include a server in the cluster. Then retry the operation. |
Explanation | To convert an existing server to be the first member of cluster, both the name of the server and name of the node where the server resides must be specified. |
Action | Specify both parameters, and retry the operation. |
Explanation | The weight of the cluster member was not valid. It must be a value in the range specified in the message. |
Action | Specify a valid value for the cluster member weight, and retry the operation. |
Explanation | When creating a cluster, the cluster member weight can be specified only when converting an existing server to be the first member of the cluster. |
Action | When you create a server cluster, do not specify the memberWeight parameter if you do not want to convert an existing server. Or, specify the serverNode and serverName parameters to convert an existing server. Then retry the operation. |
Explanation | When creating a cluster, a member replicator entry can be created only when converting an existing server to be the first member of the clsuter. |
Action | When you create a server cluster, do not specify the replicatorEntry parameter if you do not want to convert an existing server. Or, specify the serverNode and serverName parameters to convert an existing server. Then retry the operation. |
Explanation | When converting a server to be the first member of a cluster, a replicator entry can be created only if a replication domain for the cluster is also created. |
Action | If you run the convertServer step of the createCluster command, do not specify the replicatorEntry parameter unless you also run the replicatorDomain command step. |
Explanation | While validating the command, an exception was caught. |
Action | Evaluate the exception specified in the message to determine the problem. Then retry the operation. |
Explanation | The command did not run because it failed validation. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | The cell object was not found in the configuration repository. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception occurred while running the command. |
Action | Evaluate the exception specified in the message to determine the problem. Configuration changes may not have been committed. To be safe, discard any configuration changes made in this session. Then retry the operation. |
Explanation | Either a configuration object ID or a name can be used to identify a cluster, but not both. |
Action | Either specify a cluster object ID for the target object of the command, or specify a cluster name for the clusterName parameter of the command. Retry the operation. |
Explanation | The configuration object represented by the specified object ID could not be found in the configuration repository, or is not the object ID of a cluster. |
Action | Investigate the object ID, and how it was obtained, to determine if it represents a valid cluster object in the configuration repository. Specify a valid cluster object ID and retry the operation. |
Explanation | A cluster must be identified using either a configuration object ID or a name. |
Action | Either specify a cluster object ID for the target object of the command, or specify a cluster name for the clusterName parameter of the command. Retry the operation. |
Explanation | The specified cluster could not be found in the configuration repository. |
Action | Determine if the specified cluster was created, or if the correct cluster name was specified. Specify a valid cluster name and retry the operation. |
Explanation | A cluster member cannot be created because a server with the specified name is already configured on the specified node. |
Action | Determine if the name of the cluster member and node of the member were specified correctly. Specify a different name or node, and retry the operation. |
Explanation | The specified node could not be found in the configuration repository. |
Action | Determine if the specified node was created, or if the correct node name was specified. Specify a valid node name and retry the operation. |
Explanation | To create the first member of the cluster, either a template name must be specified, or the name and node of an existing server to use as the template must be specified. |
Action | Specify either the templateName paramater, or both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | To create the first member of the cluster, a template name must be specified, or the name and node of an existing server to use as the template must be specified, but not both. |
Action | Specify either the templateName paramater, or both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | To use an existing server as a template to create the first member of a cluster, both the name and node of the server must be specified. |
Action | Specify both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | The firstMember command step can run only when the creating the first member of a cluster. When creating additional cluster members, the information specified in this step is not valid. |
Action | Check the cluster name and verify that you are creating the cluster member in the intended cluster. If you are, retry the operation without specifying the firstMember command step and any of its parameters. |
Explanation | The specified template could not be found in the configuration repository. |
Action | Verify the template name was specified correctly, the template exists, and the template is for a server type of configuration object. Specify a valid server template and retry the operation. |
Explanation | The server of the first cluster member, which is used as the template when creating additional cluster members, cannot be found. |
Action | Verify the first cluster member has already been created and saved in the configuration repository. The first cluster member must be created before creating additional cluster members. Specify a template name, or template server and node, to create the first cluster member. |
Explanation | A replicator entry cannot be created for the new cluster member because no replication domain can be found which has the name of the specified cluster. |
Action | Verify that a replication domain has already been created for the cluster. If no replication domain has been created, create the replication domain and retry the operation. Alternatively, specify a value of false for the replicatorEntry parameter to skip the creation of a replication entry for the cluster member. |
Explanation | A replicator entry cannot be created for the new cluster member because an existing replicator entry with the same name was already found in the replication domain. |
Action | Verify whether the replicator entry exists for another cluster member. If it does, either choose another name for the new cluster member, or do not request the creation of a replicator entry for the cluster member. |
Explanation | The replication domain for the specified cluster cannot be deleted because no replication domain having this cluster name can be found in the configuration repository. |
Action | Verify the correct cluster name was specified, and that a replication domain exists for this cluster. If no replicaiton domain exists, specify a value of false for the deleteRepDomain parameter to skip the deletion of the replication domain. |
Explanation | The specified cluster was successfully deleted from the configuration repository. |
Action | No action is required. |
Explanation | A cluster member must be identified by specifying either a configuration object ID, or the names of the member, the node where the member resides, and the cluster to which the member belongs. |
Action | Specify a cluster member object ID for the target object of the command, or by specify the valid names for the clusterName, memberNode, and memberName parameters of the command. Then retry the operation. |
Explanation | While validating the cluster member object ID, the member name and node could not be obtained. |
Action | Verify the object ID is a valid ID for a cluster member, and not another type of configuration object. Then retry the operation. |
Explanation | The parent cluster object of the specified cluster member could not be found in the configuration repository. |
Action | Verify the correct cluster member was specified, and the cluster itself was not previously deleted. Then retry the operation. |
Explanation | The cluster name of the parent cluster could not be obtained for the cluster member during validation of the cluster member object ID. |
Action | Verify the cluster member was not previously deleted. Then retry the operation. |
Explanation | To identify a cluster member, the member name, node name and cluster name must all be specified. |
Action | Specify the clusterName, memberNode, and memberName parameters. Retry the operation. |
Explanation | The specified cluster member could not be found in the configuration repository. |
Action | Verify that the cluster member name and node name are specified correctly, and that they represent an existing cluster member. Verify the member belongs to the specified cluster. If the member does not, specify the correct values and retry the operation. |
Explanation | The server for the specified cluster member could not be found in the configuration repository. |
Action | Verify the server was not deleted without removing the cluster member. Then retry the operation. |
Explanation | The replicator entry for the specified cluster could not be found because there is no replication domain for the specified cluster. |
Action | Verify that a replication domain exists for the specified cluster. A replicator entry cannot exist without a replication domain. If you are deleting a cluster member that has no replicator entry, specify a value of false for the deleteRepEntry parameter. |
Explanation | The replicator entry for the specified cluster member could not be found in the configuration repository. |
Action | Verify that the cluster member name and node are specified correctly, and that a replicator entry was created for the cluster member. If you are deleting a cluster member that has no replicator entry, specify a value of false for the deleteRepEntry parameter. |
Explanation | The cluster member was deleted from the cluster. |
Action | No action is required. |
Explanation | The AppManagement instance, which manages Java 2 Platform, Enterprise Edition (J2EE) applications, could not be obtained. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | The node where the specified server resides could not be found in the configuration repository. |
Action | Verify the server, or the node on which it resides, was not deleted. |
Explanation | The existing server could not be converted to a member of the new cluster. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | A server could not be created for a new cluster member. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | The domain name server (DNS) hostname of the specified node could not be found. |
Action | Verify the IP network configuration of the system on which the node is defined, and the node where this operation was invoked. Verify the correct node name was specfied, and the node was not deleted from the configuration. |
Explanation | A new replicator entry for the cluster member in the cluster replicator domain could not be created. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | Checks to determine if the cluster member can belong to the specified cluster could not be performed. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | Different product versions are installed on the node and the deployment manager. |
Action | Verify the correct product versions are installed on the node and the Deployment Manager. The product installed on the node may need to be upgraded to a newer version. Consult the document to determine the supported configurations and operations of a cell which has nodes installed with different product versions. |
Explanation | The product version installed on the node is not compatible with the product version installed on the deployment manager node or the nodes of other cluster members. |
Action | Evaluate the problem text specified in the message. Verify that the correct product versions are installed on the deployment manager node and other nodes containing members of the cluster. You might need to upgrade the product installed on the node to a newer version. Consult the documentation to determine the supported configurations and operations of a cell that has nodes installed with different product versions. |
Explanation | The specified step of the specified task command could not be validated. |
Action | Evaluate the exception specified in the message to determine the problem. Then retry the operation. |
Explanation | The specified step of the specified command could not be validated. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | Because the value of the command step target is false, the step did not run. However, step parameters were specified, which indicate an intent to run the step. |
Action | To run the command step, specify true for the command step target. If you do not want to run the command step, do not specify a command step target. |
Explanation | The information specified in the firstMember command step is required when creating the first cluster member. The command step must be run. |
Action | Check the cluster name and verify you are creating the cluster member in the intended cluster. If you are, retry the operation and specify the firstMember command step along with its required parameters. |
Explanation | A new cluster member cannot be created because the specified cluster member already exists for the specified version and node. |
Action | Verify that the correct product version is installed on all the nodes and the deployment manager. You might need to updgrade the product installed on the node to a newer version. Consult the documentation to determine the supported configurations and operations for a cell that has nodes installed with different product versions. |
Explanation | The type of server that is being converted to be the first member of the cluster must be appropriate for the type of cluster that is being created. Only proxy servers can be converted into a proxy server cluster and only application servers can be converted into an application server cluster. |
Action | Change the clusterType parameter of the clusterConfig step, or change the server in the convertServer step to one of appropriate type. |
Explanation | A replication domain can only be created for cluster type APPLICATION_SERVER. |
Action | Change the clusterType parameter of the clusterConfig step, or remove the replicationDomain step. |