Row Locking
Date: 1995/09/13
Message-ID: <4374du$rip_at_nic.wat.hookup.net>#1/1
I have a question regarding deadlock detection within Oracle7, version 7.1.4, (in a Netware 3.x environment).
We have an experienced application developer who is concerned about allowing his application to accommodate "update" deadlock conditions. As the resident DBA I am trying to help.
We have done some testing within SQL*Plus to force a lock state on a single row within a table accessed by two concurrent users. The blocked user becomes "locked" indefinitely until the "blocker" either commits or roles back their transaction. Oracle on behalf of the blocked user does nothing. Is there some way, at the session or system level, that we can bias Oracle's behaviour in this regard? Can we establish a time-out so that the blocked user can proceed in an informed fashion, rather than waiting on the "blocker" to do something?
Oracle doesn't seem to do any kind of deadlock detection in this regard, other than wait for the "blocker". On hot spots within a busy table this can conceivably become problamatic.
Your feedback is greatly appreciated.
PB Received on Wed Sep 13 1995 - 00:00:00 CEST