Incorrect behavior after an uninstallation and re-installation
You might experience incorrect behavior if you uninstall then reinstall the product
without rebooting. For example, you might experience the following problems:
v
Inability to create trace logs.
v
Agents do not start.
v
Agents data is corrupt.
Reboot the system to resolve the problems.
Where Remote Deployment of agents is not supported
Remote Deployment is not supported for OMEGAMON agents. It is also not
supported in environments with a z/OS Tivoli Enterprise Monitoring Server.
Remote Deployment is not supported when the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server or the Tivoli Enterprise Portal are on the
same system as the agent. It is also not supported if the target endpoint has a
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server or the Tivoli
Enterprise Portal installed on it.
This restriction includes the following commands:
v
tacmd viewagent
v
tacmd startagent
v
tacmd stopagent
v
tacmd restartagent
v
tacmd configuresystem
v
tacmd updateagent
v
tacmd removesystem
v
tacmd createnode
v
tacmd cleardeploystatus
v
tacmd restartfaileddeployment
v
tacmd checkprereq
v
tacmd addsystem
Application Support Installer hangs
The Application Support Installer (ASI) gets to the screen indicating "Please select
which applications you would like to add support for." but hangs there. After
selecting the "Next" button, the installation hangs there and does not update the
screen. The
%TEMP%\ITM_AppSupport_Install.log
(Windows) or
\tmp\ITM_AppSupport_Install.log
(UNIX and Linux) also fails to be updated after
this point, even after waiting for hours.
Change to the directory where
setup.jar
exists, and then use
java -jar
setup.jar
to run the installer.
An agent bundle is not visible from the Tivoli Enterprise Portal
The bundle has been added to the depot and is viewable from there, but it is
missing from the list of agents available for deployment from the Tivoli Enterprise
Portal for a given node. You cannot deploy an agent from the Tivoli Enterprise
Portal if the xml version in the depot is later than the installed version because the
newer xml might contain configuration properties that the back-level agent does
not support. This issue was noticed for the DB2 agent.
Chapter 5. Installation and configuration troubleshooting
75
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...