IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей

Страница: 131 / 310

Verifying the uninstallation:
About this task
Use the following steps to verify that you successfully removed the failed
installation:
1. Verify that the installation home directory and all contents have been removed.
2. Open the Registry Editor by clicking Start > Run and typing regedt32 . Click
OK.
3. Expand the key HKEY_LOCAL_MACHINE registry key.
4. Expand the SOFTWARE registry key.
5. Verify that the Candle registry key and all sub-keys have been removed from
HKEY_LOCAL_MACHINE\SOFTWARE.
You are now ready to install IBM Tivoli Monitoring.
Incorrect behavior after an uninstallation and reinstallation
You might experience incorrect behavior if you uninstall then reinstall the product
without restarting the system. For example, you might experience the following
problems:
v
Inability to create trace logs.
v Agents do not start.
v
Agents data is corrupt.
Restart the system to resolve the problems.
Tivoli Data Warehouse database does not uninstall
When you uninstall IBM Tivoli Monitoring, the Tivoli Data Warehouse database is
not removed and the ODBC data source exists. You must remove the Tivoli Data
Warehouse database and the ODBC manually.
The agent installation log shows error AMXUT7512E
The error AMXUT7512E, which indicates that the agent was not uninstalled, might
occur when running the Distributed Monitoring Upgrade Toolkit.
The agent was not uninstalled for one of the following reasons:
v
Another uninstallation is in progress that cannot complete until the computer is
restarted.
–OR–
v
The uninstallation requires stopping a process that is currently in use by a
another component.
Refer to the lcfd.log on the endpoint and agent installation log as listed in
Table 10 to determine the exact cause of the problem.
Table 10. Installation logs
Windows UNIX-based systems
install_Dir/Install/Abort IBM Tivoli
Monitoring timeStamp.log install_Dir/logs/candle_installation.log
You can manually uninstall the operating system agent by running the command
for your platform as listed in Table 11 on page 114:
Chapter 5. Installation and configuration troubleshooting
113