Command Reference

db2ndrop - Drop Database Partition Server from an Instance

Drops a database partition server (node) from an instance that has no databases. If a database partition server is dropped, its node number can be reused for a new database partition server. This command can only be used if the database partition server is stopped.

This command is available on Windows NT and Windows 2000 only.

Authorization

Local Administrator authority on the machine where the node is being dropped.

Command Syntax

>>-db2ndrop----/n:--node_number----+---------------------+-----><
                                   '-/i:--instance_name--'
 

Command Parameters

/n:node_number
A unique node number which identifies the database partition server.

/i:instance_name
Specifies the instance name. If a parameter is not specified, the default is the current instance.

Examples

   db2ndrop /n:2 /i=KMASCI

Usage Notes

If the instance-owning database partition server (node 0) is dropped from the instance, the instance becomes unusable. To drop the instance, use the db2idrop command.

This command should not be used if there are databases in this instance. Instead, the db2stop drop nodenum command should be used. This ensures that the database partition server is correctly removed from the partition database system. To drop a node in an instance where a database exists, refer to the Administration Guide.
Note:The db2nodes.cfg file should not be edited since changing the file may cause inconsistencies in the partitioned database system.

To drop a node that is assigned to the logical port 0 from a machine that is running multiple logical nodes, all other nodes assigned to the other logical ports must be dropped first. Each database partition server must have a node assigned to logical port 0.

See Also

db2nchg - Change Database Partition Server Configuration.


[ Top of Page | Previous Page | Next Page ]