Number of lock escalations (NumLockEscals)
This parameter displays the number of times that row locks have been escalated to a table lock, including exclusive lock escalations. This parameter value is useful in determining the correct setting for the locklist and maxlocks configuration parameters.
Excessive lock escalations can occur if:
- The lock list size (locklist) is insufficient for the number of concurrent applications running
- The amount of lock list reserved for each application's use (determined by the maxlock parameter) is too small
- One or more applications are using an excessive number of locks.
Recommendation:
Most of the problems associated with the NumLockEscals parameter can be corrected by:
- Increasing the value in the locklist configuration parameter
- Increasing the value in the maxlocks configuration parameter
- Identifying applications that are using a large amount of locks and modifying them so that they use table locking rather then row locking. Using this approach could cause an increase in lock waits and time waited on locks, so care should be taken when modifying applications.
Default parameter attributes
Attribute | Default value |
---|---|
Application class | DB2DB_LOCK |
Command type | Not applicable |
Platform | All |
Icon style | Graph |
Unit | Number |
Border range | Undefined |
Alarm1 range | Undefined |
Alarm2 range | Undefined |
Scheduling (poll time) | Inherited |
Active at installation | No |
Parameter type | Consumer |
Value set by | dataCollector |
TrueSight/ BMC Helix Operations Management properties
Property | Default value |
---|---|
Monitor type | DB2 Database Lock |
Key Performance Indicator | No |
Monitor for abnormalities | Yes |
Graph by default | Yes |
Availability | No |
Response time | No |
Normal distribution | Yes |
Statistical | No |