Lock monitoring with the Db2 performance trace

Performance traces are generally activated on an as-needed basis because of their added overhead. Performance trace class 6 (specifically, IFCID 0045) indicates whether suspension is caused by contention.

This trace causes Db2 to write a trace record every time a lock is suspended and every time it is resumed. Part of the data that is recorded is the resource name that is experiencing the contention. By determining which shared resources are experiencing the lock contention, you might be able to make some design changes or other tuning actions to increase concurrency. Check for contention within IRLM, because IRLM indicates true contention over resources.