| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Orphaned Row Locks
A copy of this was sent to clifford_at_bang.com (Clifford)
(if that email address didn't require changing)
On Thu, 11 Mar 1999 15:42:14 GMT, you wrote:
>Oracle Version : 7.3
>I have an app that locks rows for updating. Now when this app crashes
>(NT) these locks are still held by oracle so that no-one can update
>said rows until the instances are killed via v$session/Instance
>manager.
>
>How do i ensure that the row locks are released when the app crashes.
>
>Thanks :-)
>
>Cliff
>Which is more important :
>The Country or it's populace?
have you looked into dead client detection with sqlnet?
<quote>
Timer Initiated Disconnect or Dead Connection Detection (SQL*Net
release 2.1 and later only).
Dead connection detection is a feature that allows SQL*Net to identify connections that have been left hanging by the abnormal termination of a client. On a connection with Dead Connection Detection enabled, a small probe packet is sent from server to client at a user–defined interval (usually several minutes). If the connection is invalid (usually due to the client process or machine being unreachable), the connection will be closed when an error is generated by the send operation, and the server process will exit. </quote>
Thomas Kyte
tkyte_at_us.oracle.com
Oracle Service Industries
Reston, VA USA
--
http://govt.us.oracle.com/ -- downloadable utilities
 |
 |