Adding and dropping nodes (partition servers)

In PATROL for DB2 UDB, database partition servers are referred to as nodes. In a multi-partitioned DB2 system, administration tasks include adding and dropping nodes, setting up the database partitions on added nodes, and managing the db2nodes.cfg file.

All these tasks are easily accomplished in the PATROL console by right-clicking on a DB2 EEE instance icon and choosing commands from the DB2 Node Administration menu.

Before you begin

Ensure that you have properly installed and configured your new server before using this command to add it to your DB2 node configuration.

To start the DBM and add a node

1. Right-click on the DB2EEE instance icon and select DB2 Node Administration > Start DBM to Add Node.
2. Specify a node number, the host name, and port number for the new node that is being added to the db2nodes.cfg file.
    You can also specify options to use for creating the tablespaces on the new node partition, and optionally can specify a particular profile to use other than the default DB2 profile to start the DBM.

3. To add the node to the db2nodes.cfgfile, stop the DBM and then restart it.

   Warning

   Note

   Additionally, the PATROL KM default port configuration must be enabled on the added node to include the node in the monitored environment. To use the partitions created on the new node, you must add the node to the database node groups.

To run the add node utility at the node to create database partitions

1. Right-click on the DB2EEE node icon and select Database Administration > Node Mgmt > Add Node to Databases.
2. select the appropriate tablespace options to create the new partitions.

If a problem occurs

When you are adding a new node, a problem might occur when you create the new partitions with temporary tablespaces if the node fails to communicate with another node from which it is attempting to retrieve the required tablespace definitions. One cause for the failure might be the timeout value set for the node to respond. Try resetting the DB2 start/stop timeout parameter in the DBM configuration.

Also ensure that the default port configuration has been enabled on the new node (see the following procedure for instructions).

To configure the default port service for an added node

1. Right-click the DB2EEE_SETUP icon and select Configuration > Configure Default Ports to get the port service information for the instance or instances that you will monitor on the added node.
2. Configure default ports with port numbers by using the following method that is appropriate for your system:
   • AIX
      Run the Configure Default Ports command and enter the port service name and beginning and ending port numbers for the selected instance. If you are configuring more than one instance, select the next instance and enter the port information for that instance. Repeat the steps until all instances are configured.

• Windows NT or Windows 2000
   Manually update the services file on the new node by adding the following lines to the file:
  DB2EEEKM startingPortNumber/tcp DB2EEEKM_END endingPortNumber/tcp

  Warning

  Note

  For Windows NT, a service name is not needed in the entry. The service name specified when using the Configure Default Ports command to configure ports on the PATROL Agent node is used internally by PATROL but is not used in the services file. The services file is located in the directory: \WinNT\system32\drivers\etc on a Windows NT system.

  Information

  Example

  The entry would look as follows if 5000 was entered for the starting port number, and 5003 for the ending port number: DB2EEEKM 5000/tcp DB2EEEKM_END 5003/tcp

• Oracle Solaris
   Update the /etc/services file or /etc/inet/services if /etc/services is a symbolic link by adding the following lines:
  DB2EEEKM serviceName startingPortNumber/tcp DB2EEEKM_END serviceNameEND _endingPortNumber/tcp

  Information

  Example

  The entry would look as follows if INSTABC was entered for the service name, 5000 for the starting port number, and 5003 for the ending port number: DB2EEEKM_INSTABC 5000/tcp DB2EEEKM_INSTABC_END 5003/tcp

To drop a node

1. Right-click on the DB2EEE instance icon and select DB2 Node Administration > Stop DBM to Drop Node.

2. Enter the number of the node that you want to drop.

   Warning

   Note

   Use the Drop Node Verify command to verify if the node exists in any database nodegroup before attempting to drop it. If a database is using the node, you must first remove the node from the database nodegroups and redistribute the data before attempting to drop the node.

To view the db2nodes.cfg file before adding or dropping a node

Right-click the DB2EEE instance icon and select DB2 Node Administration > List Node Configuration.