Chat now with support
Chat with Support

Spotlight on DB2 6.9.3 - User Guide

Spotlight on IBM DB2 LUW (Linux, Unix, and Windows)
New in This Release Getting started with Spotlight on IBM DB2 LUW Desktop features specific to Spotlight on IBM DB2 LUW Spotlight on IBM DB2 LUW drilldowns
About Spotlight on IBM DB2 LUW drilldowns Buffer Pool Analysis drilldown Client Application Analysis drilldown Database Analysis drilldown Database Manager Summary drilldown Diagnostic Log drilldown FCM Analysis drilldown Tablespace Analysis drilldown Top SQL drilldown Operating System drilldown Workload Management Analysis drilldown
Spotlight on IBM DB2 LUW alarms Spotlight on IBM DB2 LUW Options Tuning SQL statements in Spotlight on IBM DB2 LUW
Spotlight Basics
Spotlight Connections Monitor Spotlight Connections Alarms Charts, Grids And Home Page Components View | Options Troubleshooting
Spotlight History Spotlight on Windows
Connect to Windows Systems Background Information Home Page Alarms Drilldowns View | Options Troubleshooting
Spotlight on Unix About us Third-party contributions Copyright

Missing Performance Counters Alarm

The Missing Performance Counters alarm becomes active when performance counter data is unavailable. This may occur when:

  • The machine is unusually busy, or
  • The performance counter has been disabled.

To verify the performance counters are unavailable, run Microsoft Performance Monitor and look for the Memory and Processor performance objects in the Add Counters dialog for the machine being diagnosed. If these objects are not listed then they need to be enabled. To do this, download and install Exctrlst.exe from the Microsoft download site.

Run the utility and do the following:

  1. Edit the Machine Name to show the name of the machine being diagnosed.
  2. Click the Refresh button.
  3. Select Service as the sort order.
  4. Select PerfOS in the counter list.
  5. Check the Performance Counters Enabled checkbox if unchecked.
  6. Repeat steps 4–5 for the PerfDisk, PerfNet and PerfProc counters.
  7. Restart the machine being diagnosed to enable the counters.


Network Failure Alarm

This alarm becomes active when you lose the Spotlight connection to a machine under diagnosis. This may occur when:

  • The network is down (and all open connections are lost), OR
  • The remote machine is rebooted, OR
  • One of the services required by Spotlight is down.

Look for the following on the machine that has raised the alarm:

  • Is the machine running?
  • Does it respond to commands?
  • Do error messages appear on the screen or in the event logs?
  • Can it "ping" other machines successfully?
  • Can it access shared folders on the network?
  • Are the Remote Procedure Call, Remote Registry and Windows Management Instrumentation services running?

If no problems are found, try to reconnect to the machine via Spotlight.


Page Faults Alarm

This alarm is activated when the number of pages being swapped exceeds a threshold. Sustained high paging rates can adversely effect the performance of a system.

When this alarm is current, you should:

  • Look at the Processes page on the Processes drilldown to see which process is causing the paging. Look at the Page Faults/sec column. This will help you determine the cause of paging.
  • Look at the Paging chart on the Summary page of the Memory drilldown. This shows how long the high paging has been occurring. Short periods of high paging are acceptable, but if the paging rate is high for a sustained period, there may be a problem with the system.
  • Consider adding more physical memory to the system.
  • Stop unnecessary services and processes on the system.


Related Topics

Page File Location Alarm

This alarm is activated when paging is low, but the disk activity on a paging file disk is high.

You may need to investigate moving paging files to another disk.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating