Workspace troubleshooting

IBM Tivoli Monitoring > Version 6.3 > User's Guides > System p Agent User's Guides > AIX Premium User's Guide > Troubleshooting > Problems and workarounds IBM Tivoli Monitoring, Version 6.3

Workspace troubleshooting

Problems can occur with general workspaces and agent-specific workspaces.
Table 1 contains problems and solutions related to workspaces.

Workspace problems and solutions

Problem Solution
Process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE. This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Use the following steps to confirm that this problem exists and to resolve it:

In the Windows Start menu, click Run.

Type perfmon.exe in the Open field of the Run window. The Performance window is displayed.

Click the plus sign (+) in the toolbar. The Add Counters window is displayed.

Look for Process in the Performance object menu.

Complete one of the following actions:

If you see Process in the menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM Software Support.

If you do not see Process in the menu, use the Microsoft utility from the Microsoft.com Operations website to enable the PerfProc performance object.
The Process performance object becomes visible in the Performance object menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data.

Restart the monitoring agent.

Name of the attribute does not display in a bar chart or graph view. When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until sufficient space is available to display all characters of the attribute name.
You start collection of historical data but the data cannot be seen. Use the following managing options for historical data collection:

Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. For information about managing this feature including how to set the interval at which data is collected, see "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide. By setting a more frequent interval for data collection, you reduce the load on the system incurred every time data is uploaded.

Use the Summarization and Pruning agent to collect specific amounts and types of historical data. Historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 a.m. daily. At that point, data is visible in the workspace view. For information about how to modify the default collection settings, see "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide.

Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal. Sort By, Group By, and First/Last functions column are not compatible with the historical data collection feature. Use of these advanced functions makes a query ineligible for historical data collection.
Even if data collection has started, you cannot use the time span feature if the query for the chart or table includes column functions or advanced query options (Sort By, Group By, First / Last).
To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries.
For information about the historical data collection function, See "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide or the Tivoli Enterprise Portal online help .
When you use a long process name in the situation, the process name is truncated. Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. The maximum name length is 100 bytes.
Regular (non-historical) monitoring data fails to be displayed. Check the formation of the queries you use to gather data. For example, look for invalid SQL statements.
Navigator items and workspace titles are labeled with internal names such as Kxx:KXX0000 instead of the correct names (such as Disk), where XX and xx represent the two-character agent code. Ensure that application support has been added on the monitoring server, portal server, and portal client.
For more information about installing application support, see "Installing and enabling application support" in the IBM Tivoli Monitoring Installation and Setup Guide.

Parent topic:
Problems and workarounds

+
Search Tips | Advanced Search

Problem	Solution
Process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE.	This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Use the following steps to confirm that this problem exists and to resolve it: In the Windows Start menu, click Run. Type `perfmon.exe` in the Open field of the Run window. The Performance window is displayed. Click the plus sign (+) in the toolbar. The Add Counters window is displayed. Look for Process in the Performance object menu. Complete one of the following actions: If you see Process in the menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM Software Support. If you do not see Process in the menu, use the Microsoft utility from the Microsoft.com Operations website to enable the PerfProc performance object. The Process performance object becomes visible in the Performance object menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data. Restart the monitoring agent.
Name of the attribute does not display in a bar chart or graph view.	When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until sufficient space is available to display all characters of the attribute name.
You start collection of historical data but the data cannot be seen.	Use the following managing options for historical data collection: Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. For information about managing this feature including how to set the interval at which data is collected, see "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide. By setting a more frequent interval for data collection, you reduce the load on the system incurred every time data is uploaded. Use the Summarization and Pruning agent to collect specific amounts and types of historical data. Historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 a.m. daily. At that point, data is visible in the workspace view. For information about how to modify the default collection settings, see "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide.
Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal.	Sort By, Group By, and First/Last functions column are not compatible with the historical data collection feature. Use of these advanced functions makes a query ineligible for historical data collection. Even if data collection has started, you cannot use the time span feature if the query for the chart or table includes column functions or advanced query options (Sort By, Group By, First / Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. For information about the historical data collection function, See "Managing historical data" in the IBM Tivoli Monitoring Administrator's Guide or the Tivoli Enterprise Portal online help .
When you use a long process name in the situation, the process name is truncated.	Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. The maximum name length is 100 bytes.
Regular (non-historical) monitoring data fails to be displayed.	Check the formation of the queries you use to gather data. For example, look for invalid SQL statements.
Navigator items and workspace titles are labeled with internal names such as Kxx:KXX0000 instead of the correct names (such as Disk), where XX and xx represent the two-character agent code.	Ensure that application support has been added on the monitoring server, portal server, and portal client. For more information about installing application support, see "Installing and enabling application support" in the IBM Tivoli Monitoring Installation and Setup Guide.