Archives of the TeradataForum

Message Posted: Mon, 23 Nov 2015 @ 21:34:16 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

As long as the first session stays active and no commit or rollback is performed, the row lock is held by the update in that session.

In the second session, the select requests a table level READ lock. A READ lock is blocked by the WRITE lock already in place. So the SELECT in the second session will be held until the first update is completed or rolls back.

If the desire is to read the table without regard to the status of other transactions, then LOCKING FOR ACCESS should be used on the SELECT statement.

	<Prev	Next>		<<First	<Prev	Next>	Last>>