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

Locks maintained on Command Editor (DB2UDB V8) despite autocommit on

P: n/a
Hi, all

Running a query via Command Editor from a DB2UDB V8 Windows2000 client,
if I cancel the executing query the query seems to just carry on anyway
(unlike Command Center which used to confirm that it had been
cancelled) but more importantly database locks seem to be maintained
that can cause alerts on our monitoring software. Usual action is for
me to issue a commit even though I have nothing obviously running.
Didn't get this problem with CommandCenter.

Seems a bit odd. The autocommit checkbox on my Command Editor is set to
'on'.

Has anybody else encountered persistent locks like this, with this
software?

Thanks in advance for any help

Kevin

Sep 12 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.