Chat now with support
Chat with Support

Spotlight on DB2 6.10 - 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

App Sort & Join Overflow Pct graph

The App Sort & Join Overflow Percent graph relates the number of sort and hash join overflows to the total number of sorts and hash joins, respectively, generated by the application. These ratios, expressed as percentages, are determined for the application over consecutive monitoring intervals and are shown in the following series:

  • Sort ovflw —Plots the percentage of sort overflows per monitoring interval. (This percentage is based on the ratio of sort overflows to total sorts completed.)

  • Hash ovflw —Plots the percentage of hash joins that encountered insufficient sort heap per monitoring interval. (This percentage is based on the ratio of hash joins that overflowed to total hash joins completed.)

  • Hash sm ovflw —Plots the percentage of hash join overflows in which the sort heap was short by ten percent or less (per monitoring interval).

  • Hash loop —Plots the percentage of hash joins that had to resort to a less efficient algorithm because the sort heap allocated lacked sufficient space to use the standard, high-performance hashing technique. (This percentage is based on the ratio of hash join loops to total hash joins.)

The bottom of the graph shows the total sort heap allocation for all sorts during the last monitoring interval. This number can exceed the SHEAPTHRES database manager configuration parameter.

For further investigation

Access the Top SQL drilldown to identify offending SQL statements within the application.

 

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating