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
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.
3 Top Steps to Transform Bigdata to Useful Information
Here are three top processing steps to convert Bigdata to useful information.
AWS Simple Queue Service: Here is Default Retention Period
Amazon SQS’s powerful feature is you can use this for communication between distributed components. Here is its architecture and default retention period.
Scala Vs Java: Here Is Useful Syntax For Array
Here is the quick syntax of arrays declaring in Java and Scala. It is handy for programmers who wish to learn more.
Loading…
Something went wrong. Please refresh the page and/or try again.
