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

Client connection crash and Rollback..

P: n/a
Hi,

When a client application crash in the middle of a transaction, db2
keeps the locks on tables updated in the transaction whereas the
connection has been killed...there is the same behavior under oracle
as long as the server do not check (by default) the state of
connection, but we can active it in a parameter file.

Is there a way under DB2 to automatically kill connection of client
that have crashed?

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


P: n/a
Db2 will eventually clean up on the server side...when depends on the
comms protocol (for example tcp/ip the setting to check that a
connection is alive is made at the os level).

worky wrote:
Hi,

When a client application crash in the middle of a transaction, db2
keeps the locks on tables updated in the transaction whereas the
connection has been killed...there is the same behavior under oracle
as long as the server do not check (by default) the state of
connection, but we can active it in a parameter file.

Is there a way under DB2 to automatically kill connection of client
that have crashed?

Thanks

Nov 12 '05 #2

P: n/a
Thanks for answer,

do you know which parameter i have to set under window at the os level
to clean up the server side?

Thanks
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.