DB2 Version 9.7 for Linux, UNIX, and Windows

Installing IBM Tivoli Monitoring for Databases: DB2 Agent with the DB2 installer

The IBM® Tivoli® Monitoring for Databases: DB2® Agent that is installed with the DB2 product is intended for users of IBM InfoSphere® Optim™ Database Administrator. Use of the Monitoring Agent for DB2 is specifically restricted to supplying monitoring information to the IBM InfoSphere Optim Database Administrator Health and Availability monitoring feature only. Installation of the Monitoring Agent for DB2 is supported on Windows operating systems, and, root installations on Linux and UNIX operating systems.

Before you begin

When installing a DB2 product with either the DB2 setup wizard or a response file, the Monitoring Agent for DB2 is installed by default. If you install your DB2 product using a response file, you can choose to not install the Monitoring Agent for DB2 by changing the value of the INSTALL_ITMA keyword. For more details, see Response file keywords.

On Windows operating systems:

Installation of the Monitoring Agent for DB2 is supported on all platforms supported by DB2 products, except Windows Vista and Windows 2008. This support includes installing a Monitoring Agent for DB2 with a non-administrator account with elevated privileges.
If the DB2 copy being installed is the default copy, all DB2 instances are configured to use this copy of the Monitoring Agent for DB2. If this DB2 copy is not the default copy, the Monitoring Agent for DB2 instance created during the installation is configured to use the default DB2 copy.
During DB2 product installation, if a previous IBM Tivoli Monitoring for Databases product already exists on the system, and, the existing Monitoring Agent for DB2 was not installed as part of a previous DB2 product installation, the DB2 installer does not configure DB2 instances for using the Monitoring Agent for DB2. In this case, neither the pre-existing Monitoring Agent for DB2, nor the Monitoring Agent for DB2 installed as part of the DB2 product installation are used. In addition, the Monitoring Agent for DB2 instance created during this DB2 product installation is not configured to use the default DB2 copy.
If you have multiple DB2 copies on the same computer, some DB2 copies might have a Monitoring Agent for DB2 installed and some DB2 copies might not. Only one DB2 copy can be the default. When you switch DB2 default copy, you need to consider the following:
- if the current DB2 default copy had a Monitoring Agent for DB2 installed, and you switch to a DB2 copy that does not have a Monitoring Agent for DB2 installed, all Monitoring Agent for DB2 instances are unconfigured.
- if the current DB2 default copy does not have a Monitoring Agent for DB2 installed, and you switch to a DB2 copy with a Monitoring Agent for DB2, you must create and configure the Monitoring Agent for DB2 instances for all DB2 instances on the system.

On Linux and UNIX operating systems:

Installation of the Monitoring Agent for DB2 is valid for root installations only on all Linux and UNIX platforms that support the following DB2 products: DB2 Enterprise Server Edition, DB2 Workgroup Server Edition, DB2 Personal Edition, DB2 Express® Edition, DB2 Connect™ Enterprise Edition.
The Monitoring Agent for DB2 exists at the predefined location on the image media.
Multiple copies of the Monitoring Agent for DB2 are allowed on the same system, however, each Monitoring Agent for DB2 must be configured to a different DB2 copy. If a copy of the Monitoring Agent for DB2 is already installed with the current DB2 copy, the DB2 installer will not install the Monitoring Agent for DB2.

Procedure

To install the Monitoring Agent for DB2:

Choose one of the following installation methods:
- Perform the installation using the DB2 Setup wizard and follow the instructions in the wizard. The Monitoring Agent for DB2 is installed by default.
- Perform the installation using a response file. Ensure the response file keyword INSTALL_ITMA is set to YES. In a response file installation operation, the default behavior of the DB2 installer is to install the Monitoring Agent for DB2 . If INSTALL_ITMA is YES, or if INSTALL_ITMA is commented out or missing from the response file, the DB2 installer will install the Monitoring Agent for DB2. To prevent the DB2 installer from installing ITMA in a response file installation, set INSTALL_ITMA to NO.
Check the messages in the log file when the installation finishes.
- On Windows operating systems, by default the installation log file is located in the My Documents\DB2LOG\ directory. The log file uses the following format: DB2-ProductAbrrev-DateTime.log, for example, DB2-ESE-Tue Apr 04 17_04_45 2009.log.
- On Linux and UNIX operating systems, by default the installation logs are located in the /tmp directory:
  - db2setup.log
  - db2setup.err
- The itm_install.log is located in the DB2 installation path. For example, DB2DIR/itma/logs/itm_install.log, where DB2DIR represents the location where the DB2 copy is installed.

Results

The following processes are automatically started if you specified an instance name during installation:

On Windows operating systems: kudcma_instance, where instance is the name of the instance being monitored
On Linux and UNIX operating systems: kuddb2. There can be multiple kuddb2 processes running concurrently if there are multiple instances being monitored.

What to do next

On Windows operating systems, if you are the DB2 instance owner, you can start and stop the Monitoring Agent for DB2 process from the Windows Service panel. The service name is:

Monitoring Agent for DB2 - instance

where instance is the name of the instance.

On Linux and UNIX operating systems:

If you are the DB2 instance owner, you can stop the Monitoring Agent for DB2 process by using the following command:
```
DB2_DIR/bin/itmcmd agent -o instance stop ud
```
If you are the DB2 instance owner, you can also start the Monitoring Agent for DB2 process by using the following command:
```
DB2_DIR/bin/itmcmd agent -o instance start ud
```
where DB2_DIR is the directory where the current version of the DB2 database system is installed and instance is the name of the instance.
If you are logged in as root, you can cause the Monitoring Agent for DB2 to start at system boot time by issuing the following command:
```
DB2_DIR/itma/UpdateAutoRun.sh -h DB2_DIR/itma
```

Note: The Monitoring Agent for DB2 contains Tivoli Monitoring features. By default, this monitoring agent uses port 1920 for HTTP service. For more information, see the IBM Tivoli Information Center.