On Windows NT or Windows 2000, use the db2ndrop command to drop a database partition server (node) from an instance that has no databases. If you drop a database partition server, its node number can be reused for a new database partition server.
Exercise caution when you drop database partition servers from an instance. If you drop the instance-owning database partition server node zero (0) from the instance, the instance will become unusable. If you want to drop the instance, use the db2idrop command.
| Note: | Do not use the db2ndrop command if the instance contains databases. Instead, use the db2stop drop nodenum command. This ensures that the database is correctly removed from the database partition server. DO NOT EDIT the db2nodes.cfg file, since changing the file may cause inconsistencies in the partitioned database system. |
If you want to drop a node that is assigned the logical port 0 from a machine that is running multiple logical nodes, you must drop all the other nodes assigned to the other logical ports before you can drop the node assigned to logical port 0. Each database partition server must have a node assigned to logical port 0.
The command has the following parameters:
db2ndrop /n:node_number
The unique node number to identify the database partition server. This is a required parameter. The number can be from zero (0) to 999 in ascending sequence. Recall that node zero (0) represents the instance-owning machine.
The instance name. This is an optional parameter. If not given, the default is the current instance (set by the DB2INSTANCE registry variable).