Quantcast
Channel: Toad for IBM DB2 Forum - Recent Threads
Viewing all articles
Browse latest Browse all 389

RE: Issue with a SELECT ... FOR UPDATE DB2 11.1

$
0
0

Hello vilallva11,

These locks are there "by design". It means that this level of locking is expected and required. No way how to change it for FOR UPDATE clause. There is no DB/instance parameter to change it (trust IBM in this :-)), but you can try to rewrite the logic. It depends on the level of isolation you require.

Check combination of FOR READ ONLY and the USE AND KEEP UPDATE LOCKS together, isolation-clause and maybe WAIT FOR OUTCOME, but all options will need the change of the logic.

I hope it helps.

Regards
Ondrej


Viewing all articles
Browse latest Browse all 389

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>