467,883 Members | 1,231 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,883 developers. It's quick & easy.

Interesting isolation level problem

I am just confused because of the following scenario.

* I have turned on the new 8.2 registry variables skipdeleted,
skipinserted, evaluncommitted to ON
* I gave a select * from <>, it was waiting for a lock, it needed an
intent share lock on the particular table..
the lock that it was waiting on was EXclusive row lock that another
process(process-2) was having, process-2 was updating the table 500
rows at a time before
committing
* I was hoping this will not result because of the new registry
variables!!!!

I tried db2pd to get the isolation levels of the applications, but
with no joy...
How can I get the isolation level?

Jul 18 '07 #1
  • viewed: 1385
Share:
1 Reply
Hi, Arun.

It's possible that one of the updated rows from process-2 satisfies
predicates of the query. I believe that DB2_EVALUNCOMMITTED can only
avoid lock wait where the modified row does not satisfy the
predicates.

There are also some limitations to when the feature can play in, and
even issues like lock escalation to consider.

Here's a ref: http://www.ibm.com/developerworks/db...m-0509schuetz/

Regards,
- Steve P.
--
Steve Pearson, DB2 for Linux, UNIX, and Windows, IBM Software Group
"Portland" Development Team, IBM Beaverton Lab, Beaverton, OR, USA

Jul 19 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

11 posts views Thread by Markus Breuer | last post: by
9 posts views Thread by yu_sha | last post: by
3 posts views Thread by Eric Porter | last post: by
5 posts views Thread by m0002a | last post: by
1 post views Thread by Arun Srinivasan | last post: by
3 posts views Thread by RG | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.