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

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

To solve this problem, replace the view and save the workspace.
Local history migration tools move the agent operation logs to
multiple agent history locations
If you upgrade your Tivoli Enterprise Monitoring Server and Tivoli Enterprise
Portal Server after configuring historical data collection in your previous
environment, the local history migration tools move the agent operation logs,
OPLOG and OPLOG.hdr , into multiple agent history locations.
The following files are common files and may appear in multiple directories:
v khdexp.cfg
v KRAMESG
v KRAMESG.hdr
v OPLOG
v OPLOG.hdr
Only the agent that records into the specific directory will record history into the
file. The other agents record history information into their respective directories.
Unreadable tool tip information for Available EIF Receivers list of the
Situation editor
When you select the
EIF
tab of the Situation editor, you might notice an
unreadable tool tip in the Available EIF Receivers list. The problem is caused by
bad data in the TEXT column of the EVNTSERVER table. The problem has been
corrected. However, you might still experience this problem if the default event
destination (id=0) on the zOS TEMS has not been updated since the problem was
fixed.
To correct the problem, delete the default event destination entry (for example,
id=0) and recycle the hub TEMS. This will cause the Event Forwarder to rebuild
the default event destination entry in the EVNTSERVER table and the tool tip will
display correctly.
32-bit Agent Builder agent will not start on 64-bit Windows with
System Monitor Agent-installed OS Agent
A System Monitor Agent must not be installed into a system where existing IBM
Tivoli Monitoring components (including other monitoring agents) are already
installed, with this exception: Agents built with Agent Builder V6.2.2 or subsequent
may be installed alongside a System Monitor Agent, provided they run in the same
mode as the Windows System Monitor Agent. If the Windows agent runs in 32-bit
mode, only 32-bit Agent Builder agents are supported; if the Windows agent runs
in 64-bit mode, only 64-bit Agent Builder agents are supported. 32-bit Agent
Builder agents can be regenerated using Agent Builder to create 64-bit Windows
binaries that you can install with the 64-bit Windows System Monitor Agent.
Chapter 10. Monitoring agent troubleshooting
175