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
Quick SQL Interview Questions for Data Engineers (Little Tricky)
Prepare for Data Engineer interviews with quick SQL interview questions, tricky SQL queries, table creation scripts, joins, window functions, ranking, duplicate records, latest row logic, and real-world examples
AWS Glue Crawler Issue with Dynamic S3 Folder Paths? Here’s the Complete Fix
Learn how to fix AWS Glue crawler issues when S3 paths contain dynamically changing folders like hash values or UUIDs. Step-by-step beginner-friendly guide.
How to Create a Generic Stored Procedure for KPI Calculation (SQL + AWS Lambda)
In modern data engineering, building scalable and reusable systems is essential. Writing separate SQL queries for every KPI quickly becomes messy and hard to maintain. A better approach?👉 Use a Generic Stored Procedure powered by Dynamic SQL, and trigger it using AWS Lambda. In this blog, you’ll learn: What is a Generic Stored Procedure? A…
Unlocking the Power of Databricks Genie: A Comprehensive Guide
Databricks Genie is a collaborative data engineering tool built on the Databricks Unified Analytics Platform, enhancing data analytics for businesses. Key features include collaborative workspaces, efficient data processing with Apache Spark, built-in machine learning capabilities, robust data visualization, seamless integration, and strong security measures, fostering informed decision-making.
Something went wrong. Please refresh the page and/or try again.
Srinimf 