| Topic | Detail | Date |
| Locks | DB2 Universal Database isolates transactions from each other through the use of locks. A lock is a mechanism that is used to associate a data resource with a single transaction, with the purpose of controlling how other transactions interact with that resource while it is associated with the owning transaction. | Wednesday, January 18, 2006, 16:26 +05:30 |
| Lock Wait | If one transaction attempts to access a data resource in a way that is incompatible with the lock being held by another transaction, that transaction must wait until the owning transaction has ended. | Wednesday, January 18, 2006, 16:27 +05:30 |
| Deadlock | A deadlock occurs when two or more transactions are in a cycle of lock wait for one another, and a lock timeout does not break the cycle. | Wednesday, January 18, 2006, 16:28 +05:30 |
| Lock Escalation | When the DB2 Database Manager escalates a lock from a smaller lock granularity to a higher one due to insuffient lock memory space (for example, when it converts many row locks into a single table lock), this is called lock escalation. | Wednesday, January 18, 2006, 16:28 +05:30 |
| LOCKLIST | Indicates the amount of storage that is allocated to the lock list, in 4K pages. | Wednesday, January 18, 2006, 16:29 +05:30 |
| LOCKTIMEOUT | Specifies the number of seconds that an application will wait to obtain a lock. This parameter helps avoid global deadlocks for applications. | Wednesday, January 18, 2006, 16:30 +05:30 |