Managing nodes and nodegroups for a database


Database administration in a partitioned system includes managing the nodes and the data that is distributed across the nodes. In a DB2 partitioned database scheme, you use nodegroups to control data distribution across partitions. You can alter the scheme of the node-groups and redistribute data in the nodegroups from the PATROL console.

Data distribution is automatic according to the configuration established in a parallel-architected or partitioned system. Altering and redistributing nodegroups allows you to balance data loads and optimize your database operations.

With the following commands you can view the node information for a particular database, and create and manage nodegroups from the database icon menu.

To list the nodes and the catalog node for a database

  1. Right-click on the database icon and select Database Node Administration > Nodes.
  2. select one of the following commands to view all the nodes being used by the database or to view the catalog node for the database:
    • List Nodes
    • List Catalog Node

To work with nodegroups for a database

  1. Right-click on the database icon and select Database Node Administration > Nodegroups.
  2. select one of the following commands:
    • List Nodegroups
    • List Nodegroup Partitions
    • Create Nodegroup
    • Alter Nodegroup
    • Drop Nodegroup
    • Redistribute Nodegroup
       When creating a new nodegroup, you can specify all nodes or select one or more nodes to include in the group.
       With the Alter Nodegroup command, you are specifying nodes to add to or drop from an existing nodegroup. After altering the nodegroup, use the Redistribute Nodegroup command to redistribute data for the altered nodegroup. See the following procedure.

To redistribute a nodegroup

  1. Right-click on the database icon and select Database Node Administration > Nodegroups > Redistribute Nodegroup.
  2. Select one of the following distribution options:
Warning

Note

If you select either the distfile or the targetmap file option, the file must be accessible to the catalog node.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for DB2 Universal Database 9.0