Troubleshooting for remote deployment

Learn about troubleshooting for remote deployment.

Table 1 lists problems that might occur with remote deployment. This section provides information about troubleshooting remote deployment of the DB2® agent. See the IBM® Tivoli® Monitoring Troubleshooting Guide for general troubleshooting information.

This section describes problems and solutions for remote deployment and removal of agent software Agent Remote Deploy:
Table 1. Remote deployment problems and solutions
Problem Solution
Remote deploying an instance of the agent on a Windows 64 bit system in a ITM623FP1 environment using the command line failed with the following error message: KDY0005E The component UD is not installed on AC. The Agent HOSTNAME bundle requires that this component be present for the installation to proceed.
  1. On the TEMS machine where the DB2 agent bundle was added, add the KAC bundle version 062301000 into the TEMS depot from ITM 6.2.3 FP1 from the WINDOWS images. For example:
    • TEMS on Windows : 
      C:\IBM\ITM> tacmd addbundles -t AC -i
 C:\images\ITM623FP1\WINDOWS\Deploy
    • TEMS on Linux® : 
       /opt/IBM/ITM/bin/tacmd addbundles
 -t AC -i /images/ITM623FP1/WINDOWS/Deploy
  2. (Optional) check if there is an orphaned process named SETUP.EXE running on the OS agent machine and kill the process.
  3. run the tacmd command to remote deploy the DB2 agent again.

After upgrading the agent from version 6.22 fix pack 1 to version 7.1 on a Linux or a UNIX system, you restart remote instances of the agent which connect to ITM version 6.22 fix pack 2 components. The remote instances of the agent are restarted using the root ID which does not have the authority to connect to DB2 instances.

You have to define the correct user ID's for the agent instances in the kcirunas.cfg file. For more information, see http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/itm623_install226.htm

While you are using the remote deployment feature to install Db2 agent, an empty command window is displayed on the target computer. This problem occurs when the target of remote deployment is a Windows computer. (See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the remote deployment feature.)

Do not close or modify this window. It is part of the installation process and will be dismissed automatically.

The removal of a monitoring agent fails when you use the remote removal process in the Tivoli Enterprise Portal desktop or browser.

This problem might happen when you attempt the remote removal process immediately after you have restarted the Tivoli Enterprise Monitoring Server. You must allow time for the DB2 agent to refresh its connection with the Tivoli Enterprise Monitoring Server before you begin the remote removal process.

You have configured and attempted to deploy a remote instance of the agent and the operation has failed. However the Agent Event workspace does not display information explaining why the deployment operation failed.
There are a number of reasons that could result in this problem, to solve the problem you can attempt the following:
  • On Unix or Linux systems, verify that the DB2 instance to be monitored and the user name entered as the DB2 instance owner under Run As both exist on the remote machine.
  • On Windows systems, verify that you are not trying to deploy a 32 bit agent instance to monitor a 64 bit DB2 instance and that no agent instance of the same name is already deployed to the remote machine.

If this problem persists, check the ITM logs for more information.