Description

Determines whether a read transaction can access committed rows that are locked by a write transaction when the application isolation level is Read Committed (DB2 Cursor Stability) or Repeatable Read (DB2 Read Stability).

This property only applies to connections to DB2 V9.7 for Linux/UNIX/Windows and higher databases.

Valid Values

auto | useCurrentlyCommitted | waitForOutcome

Behavior

If set to auto, the driver determines whether read transactions can access currently committed data when lock contention occurs by checking the setting of the DB2 cur_commit parameter on the database server. If the cur_commit parameter is set to ON, read transactions can access currently committed data.

If set to useCurrentlyCommitted, the driver allows read transactions to access currently committed data if the data is being updated or deleted. Read transactions skip rows that are being inserted.

If set to waitForOutcome, read transactions wait for a commit or rollback operation if they encounter data that is being updated or deleted. Read transactions do not skip rows that are being inserted.

Default

auto

Data Type

String