Two-phase locking (2PL) in DBMS Theory - Mini Project: Build & Apply

Understanding Two-Phase Locking (2PL) in Databases

📖 Scenario: You are learning how databases keep data safe when many users try to change data at the same time. Two-phase locking (2PL) is a method that helps avoid problems by controlling when locks on data are taken and released.Imagine a library where many people want to borrow books. To keep things fair and safe, the library uses a rule: first, you must get all the books you want before you start reading, and you cannot take any new books after you start reading. This is like two-phase locking.

🎯 Goal: Build a simple step-by-step example that shows how two-phase locking works by creating a list of transactions, setting a lock phase, applying the locking rules, and then completing the transaction.

📋 What You'll Learn

Create a list of transactions with exact names and actions

Add a variable to track the current phase of locking

Use a loop to apply locking rules to each transaction

Complete the transaction by releasing locks in the correct phase

💡 Why This Matters

🌍 Real World

Two-phase locking is used in real databases to make sure that when many users change data at the same time, the data stays correct and safe.

💼 Career

Understanding 2PL helps database administrators and developers design systems that avoid data errors and improve reliability.

1

Create the list of transactions

Create a list called transactions with these exact entries: 'T1: read A', 'T2: write B', 'T3: read B', 'T4: write A'.

DBMS Theory

# Create the list of transactions
# Your code here

Hint

Use square brackets to create a list and put each transaction as a string inside quotes.

2

Set the locking phase variable

Add a variable called locking_phase and set it to the string 'growing' to represent the first phase of two-phase locking.

DBMS Theory

transactions = ['T1: read A', 'T2: write B', 'T3: read B', 'T4: write A']
# Set the locking phase variable
# Your code here

Hint

Use a simple assignment to create the variable and set its value to 'growing'.

3

Apply locking rules to transactions

Use a for loop with variable transaction to go through transactions. Inside the loop, add a comment line # Acquire lock for {transaction} to show the locking action during the growing phase.

DBMS Theory

transactions = ['T1: read A', 'T2: write B', 'T3: read B', 'T4: write A']
locking_phase = 'growing'
# Loop through transactions to acquire locks
# Your code here

Hint

Use a for loop and inside it write a comment showing the lock acquisition for each transaction.

4

Complete the transaction by releasing locks

Change the locking_phase variable to 'shrinking'. Then add a for loop with variable transaction to go through transactions. Inside the loop, add a comment line # Release lock for {transaction} to show the unlocking action during the shrinking phase.

DBMS Theory

transactions = ['T1: read A', 'T2: write B', 'T3: read B', 'T4: write A']
locking_phase = 'growing'
for transaction in transactions:
    # Acquire lock for {transaction}

# Change phase to shrinking and release locks
# Your code here

Hint

Assign 'shrinking' to locking_phase and use a for loop with a comment inside to show lock release.

Practice

1. What is the main purpose of Two-phase locking (2PL) in a database system?

easy

A. To allow multiple users to write to the same data simultaneously

B. To speed up database queries by skipping locks

C. To ensure transactions are executed without interfering with each other

D. To delete old data automatically after transactions

Solution

1. Step 1: Understand the role of 2PL

   Two-phase locking controls how transactions lock data to avoid conflicts.

2. Step 2: Identify the main goal

   The goal is to keep data consistent by preventing transactions from interfering with each other.

3. Final Answer:

   To ensure transactions are executed without interfering with each other -> Option C

4. Quick Check:

   2PL ensures safe transaction execution = To ensure transactions are executed without interfering with each other [OK]

Hint: 2PL controls locks to keep data safe from conflicts [OK]

Common Mistakes:

• Thinking 2PL speeds up queries by skipping locks
• Believing 2PL allows simultaneous writes on same data
• Confusing 2PL with automatic data deletion

2. Which of the following correctly describes the two phases in Two-phase locking (2PL)?

easy

A. Lock acquisition phase followed by lock release phase

B. Lock release phase followed by lock acquisition phase

C. Transaction commit phase followed by rollback phase

D. Data read phase followed by data write phase

Solution

1. Step 1: Recall the two phases of 2PL

   2PL has a phase where locks are obtained first, then a phase where locks are released.

2. Step 2: Match the correct order

   The correct order is acquiring locks first, then releasing them after work is done.

3. Final Answer:

   Lock acquisition phase followed by lock release phase -> Option A

4. Quick Check:

   2PL phases = acquire locks then release locks [OK]

Hint: Locks must be acquired before releasing in 2PL [OK]

Common Mistakes:

• Reversing the order of lock release and acquisition
• Confusing 2PL phases with commit and rollback
• Mixing data read/write phases with locking phases

3. Consider two transactions T1 and T2 using strict 2PL. If T1 locks data item X and then T2 requests a lock on X, what will happen?

medium

A. Both T1 and T2 will share the lock on X

B. T2 will immediately get the lock on X

C. T1 will release the lock on X immediately

D. T2 will wait until T1 releases the lock on X

Solution

1. Step 1: Understand strict 2PL locking rules

   In strict 2PL, a transaction holds exclusive locks until it commits or aborts.

2. Step 2: Analyze the lock request by T2

   T2 must wait because T1 still holds the lock on X and has not released it yet.

3. Final Answer:

   T2 will wait until T1 releases the lock on X -> Option D

4. Quick Check:

   Strict 2PL means waiting for lock release [OK]

Hint: New lock requests wait if current lock is held [OK]

Common Mistakes:

• Assuming locks are shared simultaneously
• Thinking locks are released immediately after use
• Believing T2 can force lock release

4. A transaction T1 acquires a lock on data item A and then releases it before completing all its operations. What problem can this cause in Two-phase locking?

medium

A. It can cause a deadlock

B. It can violate serializability and cause inconsistent data

C. It speeds up transaction processing safely

D. It prevents other transactions from accessing data

Solution

1. Step 1: Understand the 2PL rule about lock release

   In 2PL, locks should be held until the transaction finishes to ensure consistency.

2. Step 2: Analyze early lock release effect

   Releasing locks early can allow other transactions to access data prematurely, causing inconsistent results.

3. Final Answer:

   It can violate serializability and cause inconsistent data -> Option B

4. Quick Check:

   Early lock release breaks serializability = It can violate serializability and cause inconsistent data [OK]

Hint: Releasing locks too soon breaks data consistency [OK]

Common Mistakes:

• Confusing deadlock with early lock release
• Thinking early release speeds up safely
• Assuming early release blocks others

5. In a database using strict 2PL, two transactions T1 and T2 both want to update data items X and Y. T1 locks X then Y, while T2 locks Y then X. What problem can arise and how can it be resolved?

hard

A. Deadlock can occur; resolved by ordering lock acquisition consistently

B. Data corruption can occur; resolved by disabling locks

C. No problem occurs; transactions proceed normally

D. Transactions will merge automatically; resolved by splitting data

Solution

1. Step 1: Identify the problem from lock order

   T1 locks X then Y, T2 locks Y then X, creating a circular wait condition.

2. Step 2: Recognize deadlock and resolution

   This circular wait causes deadlock; it can be resolved by enforcing a consistent lock order for all transactions.

3. Final Answer:

   Deadlock can occur; resolved by ordering lock acquisition consistently -> Option A

4. Quick Check:

   Conflicting lock order causes deadlock; fix by consistent order [OK]

Hint: Consistent lock order prevents deadlocks in 2PL [OK]

Common Mistakes:

• Ignoring deadlock possibility
• Thinking disabling locks solves corruption
• Assuming transactions merge automatically