IBM Support

Abnormal termination of Situation causes TEMS to fail

Flashes (Alerts)


Abstract

If a Situation returns data that exceeds the Tivoli Monitoring Server's' maximum row buffer size, then the process overhead incurred by the enablement of automatic detailed tracing, will cause the Server to abnormally terminate. The messages KO49045 and KO49041 will appear in the Server's Operations Log file prior to the Server's termination.

Content

If you create a Situation that collects a total amount of attribute data that exceeds the 4,000 byte maximum row size you will see this problem. Typically these are Custom Situations which return large lines of a text file, and many attributes, or Situations which are written for the Log File Agent (KLO) which collect log file entries for more than one of the Situation's attributes.

As a temporary fix, locate all log entries that match the message numbers KO49045 and KO49041 in the Server's Operations Log file and stop the Situation that is referenced in these messages until APAR IV70844 is applied to all Servers in the Tivoli Enterprise. The Server's Operations Log files can be found in the Server's $CANDLEHOME/logs directory for Unix and Linux as follows:

awk '/Running:/{print $5}' $CANDLEHOME/logs/ms.env

On Windows platforms, the Server's Operations Log file name is %Candle_Home%/CMS/kdsmain.msg.

[{"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":["ITM Tivoli Enterprise Mgmt Server V6","ITM Tivoli Enterprise Mgmt Server V6"],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.3.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

TEMS RTEMS

Document Information

Modified date:
25 September 2022

UID

swg21700347