Summarization and Pruning agent schedule not affected by daylight
saving time
If after starting the Summarization and Pruning agent you allow daylight savings
time to be reached, the agent start time is now 1 hour later than the time before
the time change. The agent does not seem to be aware of the time change.
The agent is respecting flexible scheduling in this case. That it appears to be
running one hour later is an artifact of the time change. The number of minutes for
the run remains the same.
Attribute names must be kept under 28 characters long
Attribute names must be kept under 28 characters long due to the Summarization
and Pruning Agent adding suffixes to the attribute names. There are also limits in
how long the column name can be for some of the DBMS' that are supported by
Tivoli Data Warehouse.
Agent deployment operations are not completing before the TIMEOUT
expires
When running agent deployment operations, TIMEOUTs can occur because of slow
network connections or slow hardware. The agent deployment operations can
complete if you increase the TIMEOUT value. Some operations can complete even
after a timeout is returned.
Table 16. Resolutions for agent deployment operations that TIMEOUT
Problem Resolution
KDY0014E
message
Increase the Tivoli Enterprise Monitoring Server timeout value to 1200
seconds (TIMEOUT=1200). The default is 600 seconds.
On Windows: installation_dir\CMS\KBBENV.
On UNIX-based systems: installation_dir/config/
host_name_ms_Tivoli_Enterprise_Monitoring_Server_ID.config.
KDY1009E
KDY1017E
KDY1018E
KDY1022E
KDY1025E
KDY1030E
KDY1033E
Increase the OS agent timeout to 600 seconds (TIMEOUT=600). The
default is 300 seconds.
On Windows: installation_dir\CMS\KNTENV.
On UNIX-based systems: installation_dir/ux.ini. On Linux, set it in
installation_dir/lz.ini. The value must be set in seconds:
Chapter 10. Monitoring agent troubleshooting 189
To Next Page
Loading...
Need help?
General
