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
30 SQL Practice Queries with Solutions — Run Them Live
Practice 30 SQL queries with solutions, from SELECT and JOINs to subqueries and window functions. Run SQL queries live in an interactive SQL Playground.
Supercharge Your Database Skills: Try Our New Interactive SQL Plugin!
Struggling with database queries? Explore our new interactive SQL plugin to write, test, and master SQL directly in your browser. Try the live demo now!
How to Count Spark Stages by Sight and Optimize Shuffles
Want to predict execution stages before running a job? Learn how to count Spark stages by sight with code breakdowns, shuffle rules, and optimization traps.
Databricks Cluster Min & Max: How to Find and Right-Size
Learn how to find and audit Min and Max worker limits in Databricks, track real cluster usage via system tables, and prevent runaway compute costs.
Something went wrong. Please refresh the page and/or try again.
