"C:\IBM\ITM\TMAITM6\kdy_xa.exe -r DB2:FROBERTS:UD
-pc ud" (4300DFCE.0001-828:kdytasks.cpp,1066,"runCommand")
STDOUT [0 characters] is:
(4300DFCE.0002-828:kdytasks.cpp,1069,
"runCommand") STDERR [76 characters] is: Error line(391): Unable to delete file:
C:\IBM\ITM\tmaitm6\KUDCMA_DB2.exe
(4300DFCE.0003-828:kdytasks.cpp,3291,"setConfig") KDY1008E Received bad return code
[3221225477] from two-way translator
command [C:\IBM\ITM\TMAITM6\kdy_xa.exe -r DB2:FROBERTS:UD -pc ud]
(4300E020.0000-864:knt10agt.cpp,243,"getBinaryPath")
Error retrieving binary path for process ID 8.
(4300E021.0000-864:knt10agt.cpp,243,"getBinaryPath")
Error retrieving binary path for process ID 8
This error can occur when the Tivoli Enterprise Monitoring Server is restarted and
the agent displays offline even though its running because the agent did not
register a heartbeat yet.
Agents display offline in the portal client but fire situations and agent
logs report that they are running
This error can occur if the agent names in the group identified contained
embedded spaces. Agent names cannot contain embedded spaces. Edit the agent
names to remove the spaces. The CTIRA_HOSTNAME environment variable on
the agents must include a specific definition for correct agent host names.
Navigator view sorts erratically when you remove multiple managed
systems simultaneously
The Tivoli Enterprise Portal Navigator view displays erratic sorting behavior when
you remove multiple managed systems at the same time after clicking
Remove
Offline Systems
menu item from the Managed System Status view. Allow the
display to finish updating before attempting another operation
Multiple events that occur at the same time are loaded too slowly
Manually set the variable KFW_CMW_EVENT_SLEEP in
cq.ini
on Linux or
kfwenv
on Windows to less than 10 seconds:
KFW_CMW_EVENT_SLEEP=5
Desktop client performs poorly after installing Language Packs for IBM
Tivoli Monitoring
About this task
Some configuration settings for the Tivoli Data Warehouse database can cause
performance degradation. Perform the following steps from a db2cmd prompt to
correct the DB2 settings:
1.
Check the Health Monitor configuration:
db2 get dbm config | find /I "health"
2.
Turn the Health Monitor off:
db2 update dbm config using HEALTH_MON OFF
3.
Determine what databases Tivoli Monitoring connects to:
db2 list application
4.
Check system buffer pool settings on the Tivoli Enterprise Portal Server and
PROXYWH databases:
Chapter 7. Portal client troubleshooting
143
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...