By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,851 Members | 1,729 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,851 IT Pros & Developers. It's quick & easy.

sqldEscalateLocks and performances

P: n/a
I have a DB2 8.1 box on Windows XP on which I noticed some performance
problems. In this cases I see messages like this in the XP event log:

2005-05-11-07.43.54.437000 Instance:DB2 Node:000
PID:1960(db2syscs.exe) TID:4000 Appid:C0A80A9F.G441.0103CA46CA41
data management sqldEscalateLocks Probe:2 Database:JMFPROD

Locks: 1255
Target: 627

There are two java applications running queries and updates against this DB,
using the type 4 JDBC driver.
My questions are:
1) Locks on tables are raised only by insert/update/delete statements or
even by select ones?
2) How can I decrease the number of locks generated by my applications?
Would it be usefull to set the transaction isolation to
TRANSACTION_READ_UNCOMMITTED (Uncommitted read)?
3) Since I use autocommit on my connection, when are locks released?

Any other suggestions to solve my problem?

Thanks a lot.

Bye

Franco

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
1, Yes
2. It will, but think about your application if it is OK for this UR
3. After Commit or Rollback, release the lock

Nov 12 '05 #2

P: n/a
> 1, Yes

:-( Then, is the lock released closing the resultset and the statament used
to select records?
3. After Commit or Rollback, release the lock


Sorry, but I didn't understand: do yo mean that the lock is automatically
released by the autocommit engine or that I need to release it explicitly?
If I need to release, how can I do it?

Thanks a lot.

Bye

Franco
Nov 12 '05 #3

P: n/a
"Franco Lombardo" <f_********@hotmail.com> wrote in message
news:42********@x-privat.org...
1, Yes


:-( Then, is the lock released closing the resultset and the statament
used
to select records?
3. After Commit or Rollback, release the lock


Sorry, but I didn't understand: do yo mean that the lock is automatically
released by the autocommit engine or that I need to release it explicitly?
If I need to release, how can I do it?

Thanks a lot.

Bye

Franco

All locks are released when a commit takes place, regardless of how the
commit occurred. The only exception is if you open a cursor with hold, and
then the lock remains past the commit.
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.