DB2 Cursor Stablity i) Cursor Stablity Leads to Higher concurency ii) Repeatable Read Leads to Higher consistency
-
Both are True
-
i) Is Only True
-
ii) is only True
-
Neither is True
DB2 isolation levels trade off concurrency vs consistency. Cursor Stability locks only the current row, allowing higher concurrency. Repeatable Read locks all rows read, preventing changes and providing higher consistency. Both statements correctly describe these characteristics.
Both statements are true. In DB2 (and standard SQL isolation levels), Cursor Stability (CS) only holds a lock on the current row being processed and releases it as the cursor moves on, so many transactions can access the table concurrently — hence higher concurrency. Repeatable Read (RR) holds locks on all rows read until commit, preventing other transactions from changing them, which guarantees the same query re-run in the same transaction sees identical data — hence higher consistency. Since i) is true (CS → concurrency) and ii) is true (RR → consistency), 'Both are True' is correct. The other options selectively deny one of two individually correct statements, so they're wrong.