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

reconfigure the warehouse. The WAREHOUSEPRUNE table will then be in the
Tivoli Data Warehouse database, and the issue will be resolved.
Agent names and icons are displayed incorrectly
When installing portal server support from images older than v6.2.2, the support
installation might fail with no symptom, leading to names and icons related to the
agent being displayed incorrectly in the Tivoli Enterprise Portal. If this occurs,
reconfigure the portal server in the Manage Tivoli Enterprise Monitoring Services
window by right-clicking the portal server entry, and then clicking
Reconfigure .
64 bit monitoring agents are not started
If a monitoring agent is installed as an "Agent Template," an instance needs to be
created before the agent can be started. For instance, you install and start a v6.2.2
Fix Pack 1, 64-bit monitoring agent and perform a local installation of a pre-v6.2.2
Fix Pack 1 agent template, for example the v6.2 Agentless Monitoring for Windows
Operating Systems. After the installation ends, the 64-bit monitoring agent is not
running. There is no trace of the monitoring agent attempting to start in the main
installation log.
The following conditions will bring about this issue:
v installations are performed locally
v
v6.2.2 Fix Pack 1 monitoring agents are 64-bit
v
pre-v6.2.2 Fix Pack 1 monitoring agents are a template
To ensure that these monitoring agents are started, manually start them from
Manage Tivoli Monitoring Services.
Examples of monitoring agents from before v6.2.2 Fix Pack 1 for which the issue
can appear:
v DB2 Agent
v
Oracle Agent
v Microsoft SQL Server Agent
v
Sybase Server Agent
v
Microsoft Exchange Server Agent
v
Lotus Domino Agent
v
VMWare VI Agent
v
Microsoft BizTalk Server Agent
v
Microsoft Cluster Server Agent
v
Microsoft Exchange Server Agent
v
Microsoft SQL Server Agent
v mySAP Agent
v
Siebel Agent
Errors in the configuration xml file
If a tag error occurs in an XML definition file, it is displayed in the LG0 log (for
example, misspelling the tag in the pc_eventdest.xml file). In the following
example, Srv should be Server:
Chapter 10. Monitoring agent troubleshooting
177