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
Azure Data Factory (ADF): The Complete Beginner-Friendly Guide (2026 Edition)
Azure Data Factory (ADF) is Microsoft’s fully managed, cloud-based data integration and orchestration service. It helps you collect data from different sources, transform it at scale, and load it into your preferred analytics or storage systems. Whether you are working with Azure SQL, on-premises databases, SaaS applications, or big-data systems, ADF gives you a unified…
Complete Terraform CI/CD Pipeline Setup with GitHub Actions — Beginner to Advanced
The complete terraform setup example ci cd pipeline to create AWS resources using GitHub actions
AWS SageMaker + S3 Tutorial: Build, Train, and Deploy a LiDAR ML Model
This end-to-end tutorial shows how to upload LiDAR images to AWS S3, preprocess point cloud data, train an ML model in Amazon SageMaker, deploy the model, and store prediction outputs back in S3. Includes clear practical steps for beginners and ML engineers.
Why DELETE with Subqueries Fails in PySpark SQL (And How to Fix It)
Learn why PySpark SQL DELETE with WHERE IN subquery fails and how to fix it using DELETE USING, Delta tables, and join-based deletes.
Something went wrong. Please refresh the page and/or try again.
Srinimf 