Setting up the Db2 administration server (DAS) in partitioned database environments

For remote administration in partitioned database environments, additional configuration steps are necessary to configure Db2 Enterprise Server Edition (Linux®, Windows, and AIX®).

About this task

Important: The Db2 Administration Server (DAS) has been deprecated and might be removed in a future release. The DAS is not supported in Db2 pureScale® environments. Use software programs that use the Secure Shell protocol for remote administration. For more information, see Db2 administration server (DAS) has been deprecated .

During installation, the setup program creates a single DAS on the instance-owning computer. You must create additional DAS on other computers to access other coordinator partitions. The overhead of working as an administrative coordinator partition can then be spread to more than one database partition in an instance. Only if you do not use db2setup will you need to do this manually.

The directions given here are only applicable for a multi-partition database environment. If you are only running a single-partition database, then the directions given are not applicable to your environment.

Procedure

To distribute the coordinator function:

  1. Create a new DAS on the selected additional computers in the partitioned database environment.
  2. Catalog each DAS as a separate system using the discover configuration parameter.
  3. Catalog the same instance under each new system, and each time specify the same computer name used to catalog the DAS.

Example

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 database instance.

product/version:
Db2 Universal Database Enterprise Server Edition Version 8.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:
  • 0 hostA 0 hostAswitch
  • 1 hostA 1 hostAswitch
  • 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: Substitute site-specific values for the fields shown previously. For example, the following table contains example path names for some sample supported platforms:
Table 1. Example path names for supported platforms
Paths Db2 ESE for AIX Db2 ESE for Windows
install_path /usr/opt/v_r_ID C:\sqllib
instance_path /home/db2inst/sqllib C:\profiles\db2inst
das_path /home/db2as/das C:\profiles\db2as
tcp_services_file /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 Universal Database Enterprise Server Edition for AIX in Version 8, the v_r_ID is db2_08_01.

When installing , the setup program creates a DAS on the instance-owning computer. The database partition server resides on the same computer as the DAS and is the connection point for the instance. That is, this database partition server is the coordinator partition for requests issued to the instance.

If DAS is installed on each physical computer, then each computer can act as a coordinator partition, as each physical computer appears as a separate DB2SYSTEM. If different clients use different systems to connect to a partitioned database server, then DAS distributes the coordinator partition functionality and helps to balance incoming connections.