Here are three top concurrency problems in DB2. So DB2 use locking mechanism to avoid these.
DB2 Concurrency Problems
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. Dirty Read – Accessing data which is not committed 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
LATEST POSTS
Here are the reasons and resolution to fix the error Can’t Instantiate Abstract Class in Python.
by Srini
August 8, 2022 August 12, 2022
AWS’s additional services let you understand the available services for various uses. The list helps you get a comprehensive idea quickly.
by Srini
August 6, 2022 August 6, 2022
JOIN in SQL has a lot of advantages. Here are the top SQL Join interview questions in terms of DB2
by Srini
August 1, 2022 August 11, 2022
Crontab Ubuntu features and their purpose explained. This post has given the best examples for Crontab on how to work with it.
by Srini
July 30, 2022 August 3, 2022
Load more posts
Loading…
Something went wrong. Please refresh the page and/or try again.
Like this: Like Loading...