Workspaces Are Missing Or Views Are Empty; Diagnosing That Workspaces Are Missing Or Empty - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Workspaces are missing or views are empty

You can encounter a problem that workspaces are missing or views are empty. For
example, you may have workspaces that return no data.
Symptoms of the problem:
v The workspaces return no data.
v There are no child Navigator items under the agent node in the Navigator view.
v The Navigator items are labeled with internal names, such as Knt:KNT1076
v You receive message KFWITM217E: Request error: SQL1_CreateRequest failed,
v You receive message KFWITM220E: Request failed during execution.See
For more information on workspaces that relate to historical data, see "Historical
data is missing or incorrect" on page 20.
To diagnose the problem that workspaces are missing or empty, see "Diagnosing
that workspaces are missing or empty."

Diagnosing that workspaces are missing or empty

You can diagnose that workspaces are missing or empty by verifying that the
monitoring agent has been started and that the configuration is correct.
You can also check that application support has been added.
About this task
To diagnose that workspaces are missing or empty, perform the following steps:
Procedure
Preliminary diagnostics
1. Refresh the Navigator by clicking View > Refresh.
2. Verify that the monitoring agent has been started. Restart if necessary. In the
3. Verify that the monitoring agent configuration is correct.
4. If your data is missing in an Oracle Agent workspace, see "Resolving Oracle
5. Check that application support has been added. See "Resolving application
10
IBM Tivoli Monitoring: Troubleshooting Guide
See "Resolving application support problems" on page 11.
instead of the correct names (such as Disk). See "Resolving application support
problems" on page 11.
rc=209. See "Resolving application support problems" on page 11.
"Resolving monitoring agent problems" on page 14.
Tivoli Enterprise Portal, right-click the Navigator item of the monitoring agent
and click Start or Restart
DB Agent problems - diagnostic actions" on page 32. Similar problems might
exist for other monitoring agents.
support problems" on page 11.