The Administration Server provides services to support client tools that:
Use the dasicrt command to create an Administration Server. You must run this command on the machine where you have DB2 physically installed and have root authority.
The syntax of the dasicrt command is as follows:
||where DB2DIR||= /usr/lpp/db2_05_00||on AIX|
||= /opt/IBMdb2/V5.0||on Solaris|
and where ASName is the name of the Administration Server, which is composed of a string of up to eight alphanumeric characters long. See Appendix F. "Naming Rules" for more information.
|Note:||If you are running NIS or NIS+, you need to set up the user and group names
in such a way that:
Because a user ID can only own one instance, you must have a separate user ID to own each Administration Server that you create.
It is possible to add an instance to any machine. If you use different machines to create instances, then the list of instances that is stored on any machine may not be a complete list. We recommend creating every instance on one machine, so that the list of instances is complete on that machine. We also recommend that this node be the Administration Server node.
You use the name of the Administration Server to set up the directory
structure and access permissions.
Use the db2admin start command to start the Administration
Server (refer to "Starting the Administration Server" for more information). When you reboot the system, it is
By adding a system that has an Administration Server to the Control Center, you are designating the corresponding database partition server (that resides on the same machine as the Administration Server) as the Control Center's connection point to the entire instance. The system specified becomes the coordinator node for requests that are issued from the Control Center.
You may want to consider distributing the coordinator function among other database partition servers in the instance. To do this:
[ DB2 List of Books | Search the DB2 Books ]