467,926 Members | 1,498 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

DB2 performance variables

Does anyone know of any problems on setting the following db2
environment variables?

DB2_EVALUNCOMMITTED=ON
DB2_SKIPINSERTED=ON
DB2_SKIPDELETED=ON

Also is it correct to assume the effect of those settings would be the
same as running a query "WITH UR" ?

Thank you

Leo

Apr 21 '06 #1
  • viewed: 2290
Share:
2 Replies
<le**********@gmail.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Does anyone know of any problems on setting the following db2
environment variables?

DB2_EVALUNCOMMITTED=ON
DB2_SKIPINSERTED=ON
DB2_SKIPDELETED=ON

Also is it correct to assume the effect of those settings would be the
same as running a query "WITH UR" ?

Thank you

Leo


There are some circumstances when an application is coded in a certain way,
where you might not want to use the settings. For more information on when
this might be, see this link:
http://www-128.ibm.com/developerwork...m-0509schuetz/

These are not really performance settings, but they can minimize lock
contention, so if you have a lot of lock wait time in your application you
may be able to increase performance. Also, these settings can "sometimes" be
useful in preventing deadlocks when application programs are not coded in
the proper way that would avoid them.

Using these settings is not the same as running a query "WITH UR" although
in some very specific circumstances with specific queries, the result may be
the similar in that lock wait time is eliminated..

Note that the above settings are ignored on queries which use the RR
isolation level.
Apr 21 '06 #2
le**********@gmail.com wrote:
Does anyone know of any problems on setting the following db2
environment variables?

DB2_EVALUNCOMMITTED=ON
DB2_SKIPINSERTED=ON
DB2_SKIPDELETED=ON

Also is it correct to assume the effect of those settings would be the
same as running a query "WITH UR" ?

That is incorrect. WITH UR will see uncommitted rows. The variables
above skip uncommitted rows.

DB2_SKIPINSERTED is safe (there is nothing wrong about not seeing a new
row that isn't committed yet).

The other two may or may not be safe depending on your app.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Apr 22 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by pragile | last post: by
115 posts views Thread by Mark Shelor | last post: by
2 posts views Thread by Lalit Singh | last post: by
13 posts views Thread by atlaste | last post: by
1 post views Thread by webdevaccount | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.