Spotlight on DB2 6.9.3 - User Guide

Paging File Alarm

This alarm is activated when the utilization of the paging file exceeds a threshold.

When this alarm is active you should:

• Look at the Processes page of the Processes drilldown. Look at the Virtual MB column to see which applications are using the most virtual memory.
• Some applications (such as Microsoft Exchange or Microsoft SQL Server) can have their memory utilization limited.
• Close any superfluous processes.
• Look at increasing the size of the page file.
• Look at increasing the amount of RAM in the machine.

Related Topics

Processes Page

Paging File Disk Location Alarm

This alarm becomes active when there is more than one paging file on a single physical disk.

This can cause performance degradation – especially on IDE disks. IDE disks allow only a single disk operation to be active on the bus at any time.

To rectify this:

1. Open the Windows Control Panel.
2. Open the System control panel.
3. Click the Advanced tab.
4. Choose Performance Settings, and change the paging file allocations.

Percentage Bandwidth Alarm

The total network bandwidth capacity of the specified network card is nearing the limit where it is saturating the network link. If this is happening regularly, look at:

• The NBT page of the Network drilldown to see if any users or other systems are copying an inordinate level of data between systems.
• Moving network applications or shared files to another machine to balance the load.
• Upgrading the network subsystem to a faster technology.
• Adding an additional network card to the machine and configuring the system to utilize it.

Tip: If there are multiple network cards on the target system, use the Windows Network Card Display options in the Spotlight on Windows Options window to choose the one whose data you want to display.

Related Topics

NBT Page

Windows Network Card Display

Physical Memory Usage Alarm

This alarm becomes active when a process is suffering a potential memory leak.

A memory leak occurs when a program continues requesting memory over a period without releasing any memory.

For some programs (such as Spotlight) this behaviour is expected as the program stores information over an extended period for dynamic near-history analysis.