Let us assume
Transaction T1#: Initiated on 2015-10-30 10:25:41.380
Transaction T2#: Initiated on 2015-10-30 10:25:41.580
The above two transactions are initiated through application.
T1# & T2# requires same resource (both looking for same resource),
A specific resource bind at T1# and T1# transaction unexpectedly exit(in the middle of its execution) from application and roll-back operation not done on this transaction T1# is still alive at DB server side.
-
What about T2# execution status (it waiting for resource bind at T1#)
? -
How much time T2# it’s going wait?
-
How system can detect the deadlock in this case?
-
Is it(T2#) in waiting for the resource until T1# connection exit (session time-out) ?
(OR) - System sends any acknowledgement to T2#
waiting for vital suggestion to implement transactions at application level.
Note: I would like to know how oracle system will manage the shared resource, when system ensures above criteria.