Chatee ahora con Soporte
Chat con el soporte

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

Instance Sort & Hash Join Exceptions graph

The Instance Sort & Hash Join Exceptions graph tracks the total number of sort and hash joins that operated in less than optimal environments in the database during consecutive monitoring intervals. These sort and hash joins, known as exceptions, are likely to impact sort performance negatively. The totals are shown in the following series:

  • Post thresh sorts —Plots the number of sorts that were allocated less memory than the amount defined by the database SORTHEAP parameter. The database manager allocated this smaller sort heap to avoid exceeding the SHEAPTHRES value—the total amount of memory in the database committed to active sorts. 

  • Post thresh joins —Plots the number of hash joins that were allocated less memory than the amount defined by the database SORTHEAP parameter. The database manager allocated this smaller sort heap to avoid exceeding the SHEAPTHRES value—the total amount of memory in the database committed to active sorts.

  • Piped sort rejects —Plots the number of non-piped sorts—that is, sorts that needed to route the final, sorted data through temporary files before sending it to the requester. Temporary files were used because the sort heap was not large enough to serve as both a sorting workspace and a temporary storage location for the sorted data.

 

 

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación