Chat now with support
Chat with Support

Spotlight on SAP ASE 2.11 - User Guide

Spotlight on SAP ASE
Background Information Desktop Features Connect to SAP ASE Spotlight® on SAP ASE Drilldowns Spotlight® on SAP ASE Alarms Glossary
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

Blocked Process Alarm

The Blocked Processes button in the CPU panel shows the number of processes waiting on information to become available in memory.

Processes can also become blocked when they are waiting for:

  • disk I/O completion,
  • network I/O completion, or
  • a shared resource.

A high level of blocked processes may indicate an under-configured machine.

The type of alarm that is activated is determined by the number of blocked processes waiting on information.

 

Related Topics

Input Error Packets Flow Alarm

The Input Error Flow represents the number of erroneous network packets coming in to the machine per second.

The Input Error Packets Flow alarm may warrant investigation as even a low error rate can indicate network problems.

The type of alarm that is activated is determined by the number of erroneous network packets coming in to the machine every second.

 

Related Topics

Output Error Packets Flow Alarm

The Output Error Flow represents the number of erroneous network packets sent by the machine per second.

The Output Error Packets Flow alarm may warrant investigation as even a low error rate can indicate network problems.

The type of alarm that is activated is determined by the number of erroneous network packets sent by the machine every second.

 

Related Topics

Page In Alarm

A large number of page-ins may be a symptom of a large number of recent page-outs. To find out what process is reading these pages in, check the resident size of the processes you are running, and see which ones are increasing in size.

A large number of page-ins may also occur when a large process has just stopped, and the kernel decides to fill that space with memory pages owned by other processes. Make sure that an important process hasn't died unexpectedly.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating