Procedure:
To remove the DAS:
v On Windows operating systems:
1. Log on to the machine using an account or user ID that has the correct authorization to remove a service.
2. Stop the DAS, using db2admin stop.
3. Backup (if needed) all the files in thedb2das00 subdirectory under the sqllib subdirectory.
Note: This example assumesdb2das00 is the name of the DAS to be removed. It is possible to have a DAS with a name other than DB2DAS00 if a user has created a DB2 instance that has the name DB2DAS00. In this case, the DAS will be named DB2DAS01 (or, if that is taken, DB2DAS02 and so forth). You should look for the service with the “DB2DAS” prefix to identify the specific DAS from the list of several DAS that may exist. You can use the db2admincommand without any options to list all DAS.
4. Drop the DAS, using db2admin drop.
v On UNIX operating systems:
1. Login as a user with DASADM authority.
2. Run the startup script using one of the following:
. DASHOME/das/dasprofile (for Bourne or Korn shell) source DASHOME/das/dascshrc (for C shell)
whereDASHOME is the home directory of the DAS owner.
3. Stop the DAS using the db2admin command as follows:
db2admin stop
4. Back up (if needed) all the files in thedas subdirectory under the home directory of the DAS.
5. Log off.
6. Log in asroot and remove the DAS using the dasdrop command as follows:
dasdrop
The dasdrop command is found in theinstance subdirectory under the subdirectory specific to the installed DB2 version and release.
Note: The dasdrop command removes thedas subdirectory under the home directory of the DB2 administration server (DAS).
Related reference:
v “db2admin - DB2 Administration Server” in the Command Reference
Setting up DAS with Enterprise Server Edition (ESE) systems
Procedure:
The following information shows the steps necessary to configure DB2 ESE servers (Linux, Solaris, Windows NT, Windows 2000, Windows .NET, HP-UX, and AIX) for remote administration using the Control Center.
During installation, the setup program creates a single DAS on the
instance-owning machine. You must create additional DAS on other machines to allow the Control Center or the Configuration Assistant access to other coordinator nodes. The overhead of working as an administrative coordinator node can then be spread to more than one partition in an instance. The install program will create the DAS on all nodes that it is run on. Only if you do not use db2setup will you need to do this manually.
The directions given here are only applicable for a partitioned ESE
environment. If you are only running on a single partition ESE system, then the directions given are not applicable to your environment.
To distribute the coordinator function:
1. Create a new DAS on the selected additional machines in the partitioned database system.
2. Catalog each DAS as a separate system in the Control Center or Configuration Assistant.
3. Catalog the same instance under each new system, and each time specify the same machine name used to catalog the DAS.
There are two aspects to configuration: That which is required for the DB2 Administration Server (DAS), and that which is recommended for the target, administered DB2 instance. In the three sections which follow, a section is
devoted to each of the two configuration topics. Each of the configuration topics is preceded by a section describing the assumed environment.
Example Environment product/version:
DB2 UDB ESE V8.1 install path:
install_path TCP services file:
services DB2 Instance:
name: db2inst owner ID:
db2inst instance path:
instance_path
nodes: 3 nodes, db2nodes.cfg:
v 0 hostA 0 hostAswitch v 1 hostA 1 hostAswitch v 2 hostB 0 hostBswitch DB name:
db2instDB DAS:
name: db2as00 owner/user ID:
db2as instance path:
das_path install/run host:
hostA
internode communications port:
16000 (unused port for hostA and hostB)
Note: Please substitute site-specific values for the above fields. For example, the following table contains example pathnames for some sample supported ESE platforms:
Table 2. Example Pathnames for Supported ESE Platforms
Paths DB2 UDB ESE for AIX DB2 UDB ESE for Solaris DB2 UDB ESE for Windows
install_path /usr/opt/<v_r_ID> /opt/IBM/db2/<v_r_ID> C:\sqllib
instance_path /home/db2inst/sqllib /home/db2inst/sqllib C:\profiles\db2inst
das_path /home/db2as/das /home/db2as/das C:\profiles\db2as
tcp_services_file /etc/services /etc/services C:\winnt\system32
\drivers\etc\services
In the table,<v_r_ID> is the platform-specific version and release identifier.
For example in DB2 UDB ESE for AIX in Version 8, the<v_r_ID> is db2_08_01.
When installing DB2 UDB ESE, the setup program creates a DAS on the instance-owning machine. The database partition server resides on the same machine as the DAS and is the connection point for the instance. That is, this database partition server is the coordinator node for requests issued to the instance from the Control Center or the Configuration Assistant.
If DAS is installed on each physical machine, then each machine can act as a coordinator node. Each physical machine appears as a separate DB2SYSTEM in the Control Center or Configuration Assistant. If different clients use different systems to connect to a partitioned database server, then this will distribute the coordinator node functionality and help to balance incoming connections.