delete-node-config

deletes a node that is not enabled for remote communication

Synopsis

asadmin [asadmin-options] delete-node-config [--help]
node-name

Description

The delete-node-config subcommand deletes a node that is not enabled for remote communication from the domain. This subcommand does not require the Distributed Component Object Model (DCOM) remote protocol or secure shell (SSH) to be configured.

This subcommand can delete only a node that is not enabled for remote communication. The subcommand for deleting other types of nodes depends on the type of the node:

A node that is enabled for remote communication over DCOM must be deleted by using the delete-node-dcom(1) subcommand.
A node that is enabled for remote communication over SSH must be deleted by using the delete-node-ssh(1) subcommand.

To determine whether a node is enabled for remote communication, use the list-nodes(1) subcommand.

No \{product---name} instances must reside on the node that is being deleted. Otherwise, the subcommand fails. Before running this subcommand, delete any instances that reside on the node by using, for example, the delete-instance(1) subcommand or the delete-local-instance(1) subcommand.

Note	The predefined node `localhost-`domain cannot be deleted.

This subcommand is supported in remote mode only.

Options

asadmin-options: Options for the asadmin utility. For information about these options, see the asadmin(1M) help page.
--help
-?: Displays the help text for the subcommand.

Operands

node-name: The name of the node to delete. The node must not be enabled for communication over DCOM or SSH. Otherwise, an error occurs.

Examples

Example 1 Deleting a Node That Is Not Enabled for Remote Communication

This example deletes the node sj03, which is not enabled for remote communication.

asadmin> delete-node-config sj03

Command delete-node-config executed successfully.

Exit Status

0: command executed successfully
1: error in executing the command