3 Top DB2 Concurrency Problems and Need of Locking

Here are three top concurrency problems in DB2. So DB2 use locking mechanism to avoid these.

DB2 Concurrency Problems

  1. Lost updates- Two processes A and B Accessing same row. A is updated the row, and then B also updates the same row. So A ‘s updates are lost.
  2. Dirty Read – Accessing data which is not committed
  3. Unrepeatable read- without concurrency causes you to get different data each time you read.

Because of all the above reasons, DB2 apply Locks on the resources.

Related Posts


DB2: How to Understand B-Tree Structure of Index

Here is the top B-Tree index mechanism that followed in DB2. It is a helpful explanation for DB2 developers.


Something went wrong. Please refresh the page and/or try again.

Author: Srini

Experienced software developer. Skills in Development, Coding, Testing and Debugging. Good Data analytic skills (Data Warehousing and BI). Also skills in Mainframe.