Brother-Eagle® DB2 Performance
Advice: Timeouts

This value represents the total number of lock timeouts that have occurred (Brother-Eagle V2.1 and earlier), or the delta value for the number of timeouts that have occurred during the most recent sampling interval (Brother-Eagle V2.2 and higher).

A lock timeout means that a connection had to wait the full amount of the LOCKTIMEOUT configuration parameter time before DB2 rolled back the transaction. Lock timeouts can cause application performance to rapidly deteriorate, especially if the LOCKTIMEOUT time is set greater than 10 seconds.

• Brother-Eagle will indicate a warning if 5 or more timeouts have occurred.
• Brother-Eagle will indicate an alert if 10 or more timeouts have occurred.
• To view current locks, Right Click on Locks Currently Waiting and select “Show Locks”. Authorized users can terminate connections holding locks.

Locking problems are a symptom of poor SQL performance. Lock timeouts are prone to occur when the index physical design does not support the statement workload. If you find timeouts repeatedly occurring on certain tables, carefully review the indexes on the tables to ensure there are no indexes that have very low cardinalities, skew, or redundant indexes. You can also use Brother-Panther™ to find insert and update statements with the highest aggregate CPU costs - these statements will direct you to tables that may have index problems.

View full list of DB2 LUW advice topics