IBM Books

Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Step 10. Set up Discovery


If you are not planning on using the CCA or the Control Center, you can skip this step and proceed to the next step.

You must configure Discovery, a feature that is used by the CCA and Control Center, to retrieve information about systems on your network. Specifically, you must update instance lists and the Administration Server configuration to ensure that Discovery retrieves the correct information.

Update Instance Lists
If you created more than one Administration Server in your partitioned database system and then created instances on one of the machines that has an Administration Server on it, you should verify that the other Administration Servers are aware of all the instances. They may not be aware of all of them because the instance lists on some machines will be incomplete until you run the db2iset command or the db2start command on the instance.

To ensure that the Administration Servers are aware of all the instances, perform the following steps:

  1. For each Administration Server, run the db2set -l command to display the list of instances known to it.

    If this list of instances includes all the instances that you want the Administration Server to recognize, skip the following steps and go to "Update the Administration Server Configuration" below. If this list does not include all the instances, go to the next step.

  2. For each instance that was not included in the list generated by the db2set -l command, check that the db2nodes.cfg file contains a line for the machine on which the Administration Server resides. If the machine on which the Administration Server resides is not in the db2nodes.cfg file, it must be added. For more information on how to add this entry, see to"Step 5. Create the Node Configuration File" (for AIX) or "Step 8. Create the Node Configuration File" (for Solaris).

  3. Update the instance lists manually by performing the following steps:

    1. Log in as root.

    2. Run the db2iset -a instance_name command to add the instance.

    If you don't update the instance lists manually, they will be updated automatically by DB2 when you run the db2start command on an instance. DB2 uses the node configuration file (db2nodes.cfg) to determine the machines on which the instance is defined and updates the instance lists on those machines. Therefore, if you didn't create an instance on the same machine as the Administration Server, the server will not recognize that the instance exists until you run the db2start command for that instance. To ensure that the Administration Server can return information about all instances in the partitioned database system, you should use the db2iset command to update the list of instances manually.

Update the Administration Server Configuration
By default, the install program sets the DB2SYSTEM registry value to the TCP/IP hostname. The system names that are retrieved by Discovery are the systems on which an Administration Server resides. Discovery uses the database partition server that is on the same machine as the Administration Server as the coordinator node when connections are established.

There are two ways of updating an Administration Server's configuration:

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]