Workspace troubleshooting

Learn about workspace troubleshooting.

Table 1 shows problems that might occur with workspaces. This chapter provides agent-specific troubleshooting information. See the IBM® Tivoli® Monitoring Troubleshooting Guide for general troubleshooting information.

Table 1. Workspace problems and solutions
Problem	Solution
The 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 there is sufficient space to display all characters of the attribute's name.
At the bottom of each view, you see the following Historical workspace KFWITM220E error: Request failed during execution	Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view.
You start collection of historical data but the data cannot be seen.	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. See Agent-specific installation and configuration for the monitoring agent in the Installation and Configuration Guide for the agent for information about managing this feature, including how to set the interval at which data is collected. By setting a more frequent interval for data collection you reduce the load on the system incurred every time data is uploaded. You use the Summarization and Pruning monitoring agent to collect specific amounts and types of historical data. Be aware that historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 AM daily. At that point, data is visible in the workspace view. See the IBM Tivoli Monitoring Administrator's Guide to learn how to modify the default collection settings.
No data is displayed in the Database workspace.	The Database workspace only shows the active databases, which are the databases for which an active connection exists. The live external connection might be the result of an application connecting or the result of a db2 connect. Also, monitoring only occurs for active databases. When the connection becomes inactive, the database disappears from the Database workspace, and monitoring stops for this database.
DB2® workspaces become empty with a busy hourglass for a while, when the DB2 agent is monitoring a partitioned DB2 database.	This problem occurs because a DB2 partition is unavailable, and there isDB2 time-out and retry activities. When a partition is unavailable, the duration after which the error status is returned is determined by the Fast Communications Manager (FCM) settings, which include the max_connretries parameter (Node connection retries) with the default value of 5 retries, and the conn_elapse parameter (Connection elapse time) with the default value of 10 seconds. When the default values of the two parameters are used, there is a 50-second delay for each DB2 API call while there are a lot of API requests for the agent to make. In this period of time, the workspaces are empty with a busy hourglass. To reduce the empty workspace time, you can set a smaller value for the max_connretries parameter or the conn_elapse parameter.