General situation problems

This topic provides information about general situation problems.

Table 1 lists problems that might occur with specific situations.
Table 1. Specific situation problems and solutions
Problem Solution
You want to change the appearance of situations when they are displayed in a Workspace view.
  1. Right-click an item in the Navigation tree, and click Situations.
  2. In the Situation Editor window, select the situation that you want to modify.
  3. Use the Status pull-down menu in the lower right of the window to set the status and appearance of the Situation when it triggers.
    Important: This status setting is not related to severity settings in IBM® Tivoli Enterprise Console®.
Monitoring activity requires too much disk space. Check the RAS trace logging settings that are described in Setting RAS trace parameters. For example, trace logs grow rapidly when you apply the ALL logging option.
Monitoring activity requires too many system resources.

Table 1 describes the performance impact of specific attribute groups. If possible, decrease your use of the attribute groups that require greater system resources.

A formula that uses mathematical operators appears to be incorrect. For example, if you were monitoring Linux®, a formula that calculates when Free Memory falls under 10 percent of Total Memory does not work: LT #'Linux_VM_Stats.Total_Memory' / 10 This formula is incorrect because situation predicates support only logical operators. Your formulas cannot have mathematical operators.
Tip: The Situation Editor provides alternatives to math operators. Regarding the example, you can select % Memory Free attribute and avoid the need for math operators.
If you are running a version of the DB2® agent prior to 6.2, and you choose to alter the views to include a new attribute, data for this attribute is not displayed and you see a blank column in this view. To enable Unicode and other features, upgrade the DB2 agent to IBM Tivoli® Monitoring, Version 6.2.0.
You see the 'Unable to get attribute name' error in the Tivoli Enterprise Monitoring Server log after creating a situation.

Ensure that the agent attribute files are installed on the Tivoli Enterprise Monitoring Server.

The following example shows a typical log entry when you have this problem:

(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \
  Unable to get attribute name for tablename/column \
  <UAG524400.UA4>. Ignored.
Situations are triggered in the Tivoli Enterprise Monitoring Server, but events for the situation are not sent to the Tivoli Enterprise Console server. The Tivoli Enterprise Monitoring Server is properly configured for event forwarding, and events for many other situations are sent to the event server. None. This is a limitation of the Tivoli Enterprise Monitoring Server event forwarding function. Situations that only monitor other situations do not send events to the event server.

This condition can occur when a situation is only monitoring the status of other situations. The event forwarding function requires an attribute group reference in the situation in order to determine the correct event class to use in the event. When the situation only monitors other situations, no attribute groups are defined and the event class cannot be determined. Because the event class cannot be determined, no event is sent.