eG Help

Nothing can degrade the performance of the server like a resource-hungry or a long-running query! When such queries execute on the server, they either hog almost all the available CPU, memory, and disk resources or keep the resources locked for long time periods, thus leaving little to no resources for carrying out other critical database operations. This can significantly slowdown the database server and adversely impact user experience with the server. To ensure peak performance of the DB2 UDB server at all times, such queries should be rapidly identified and quickly optimized to minimize resource usage. This can be done using the IBMDb2LngRunQryTest.

This test auto-discovers the DB2 UDB database instances, tracks the currently executing queries on each database and determines the number of queries that have been running for a long time.

Outputs of the test : One set of results for each DB2 UDB server instance being monitored

Measurement	Description	Measurement Unit	Interpretation
NumberOfLongRunQury	Indicates the number of queries currently executing on this database that have been running for more time than the configured ELAPSED TIME.	Number	The detailed siagnosis of this measure shows the name and ID of application, name of the user, time takne in seconds, CPU time in seconds, query cost estimation, number of reads and writes and SQL text.
MaxElapsedTime	Indicates the maximum time taken by this database for executing the queries.	Seconds	Ideally, a low value is desired for this measure.