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

Details in the UOW Details pane

All of the details shown in the UOW Details pane are listed below in alphabetic order. This pane is available on the Unit of Work sub drilldown for the Current SQL tab in the Top SQL drilldown.

Initially, details are shown in Spotlight's default order. You can sort and arrange them in different ways using options on the right-click menu for column headers.

Statement Details

Value

Agents

The number of concurrent agents currently executing a statement.

Agents Top

The maximum number of agents that have been used so far during execution of a statement. The number provides a measure of how well intra-query parallelism is being implemented.

Application Creator

The authorization ID of the user who pre-compiled the application that is running a statement.

Blocking Cursors

This value indicates whether a statement uses cursor blocking for data transfer. Blocking can reduce overhead and improve performance by retrieving a block of rows in a single operation. One of the following can be shown:

  • UNAMBIG is shown when only unambiguous cursors are blocked.

  • ALL is shown when both ambiguous and unambiguous cursors are blocked.      

  • NO is shown when cursors are not blocked.

Consistency Token

The consistency token for the package that contains a statement. Like statement package version, this helps to identify the version of the package. It is useful in situations where there are multiple versions for a certain combination of package name and creator.

Cursor Name

The name of the cursor opened for a statement. If the statement does not use a cursor, no value is shown.

Degree of Parallelism

The degree of parallelism requested when a statement was bound. Check the value in the Agents Top column to see if the statement reached the maximum level of parallelism.

Estimated Cost (timerons)

The estimated execution cost for a statement. Cost is shown in timerons. The estimate is made by the SQL compiler.

Estimated Rows

The estimated number of rows a statement will return. The estimate is made by the SQL compiler.

Statement Type

The type of SQL for a statement. Either STATIC or DYNAMIC is shown.

Statement Operation

The operation that is currently being processed or was most recently processed for a statement. The operation can be any of the following:

  • CALL

  • CLOSE

  • COMPILE

  • DESCRIBE

  • EXECUTE

  • EXECUTE IMMEDIATE

  • FETCH

  • FREE LOCATOR

  • OPEN

  • PREPARE

  • PREP_COMMIT

  • PREP_EXEC

  • PREP_EXEC

  • SELECT

  • STATIC COMMIT

  • STATIC ROLLBACK

Statement Node

The number of the database partition where a statement is being executed.  

Statement Package Name

For static SQL, this is the name of the package that contains a statement. For dynamic SQL, this is the location identifier for a statement in the package cache.

Statement Package Version

The version identifier for the package that contains a statement. Like the consistency token, this helps to identify the version of the package. It is useful in situations where the version of a package was determined at precompile time for an embedded SQL program with the VERSION keyword. If a version was not specified at precompile time, a value is not shown.

Statement Section Number

The internal section number in the package that contains a statement.

Statement Start Time

The time statement execution started. The timestamp includes year, month, date, and hour, in that order.

Statement Stop Time

The time statement execution stopped. The timestamp includes year, month, date, and hour, in that order.

 

Related Topics

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating