Re: Puzzle - Abandoned Terminal.
- From: Hemant K Chitale <hemantkchitale@xxxxxxxxx>
- To: TESTAJ3@xxxxxxxxxxxxxx
- Date: Tue, 15 Feb 2011 21:18:21 +0800
DCD would come into play if the client terminal has "gone away' but not if
it is just idle (and connected) waiting for the user's next command.
Also you might have the sequence wrong. It wouldn't be the transaction
closing the session but the other way round (in a manner of speaking).
Hemant K Chitale
sent from my smartphone
On 15 Feb 2011 21:08, <TESTAJ3@xxxxxxxxxxxxxx> wrote:
> I would think it could sit there forever, but if you have like sqlnet
> timeout, that would force the "dead" transaction to close the session and
> rollback. I know thats what I've used in the past.
>
> joe
>
> _______________________________________
> Joe Testa, Oracle Certified Professional
> Senior Engineering & Administration Lead
> (Work) 614-677-1668
> (Cell) 614-312-6715
>
>
>
>
>
>
> From:
> Howard Latham <howard.latham@xxxxxxxxx>
> To:
> ORACLE-L <oracle-l@xxxxxxxxxxxxx>
> Date:
> 02/15/2011 08:06 AM
> Subject:
> Puzzle - Abandoned Terminal.
> Sent by:
> oracle-l-bounce@xxxxxxxxxxxxx
>
>
>
> We were just chatting about the problem of users abandoning their
> terminals
> and the question arose - How long could a user leave an uncommitted
> transaction
> before it got rolled back?. Which mechanism do we thionk would eventually
> deal with it?
>
> I know the DBA gets called if a deadlock occurs but theoretically how long
> could it sit there.
>
> --
> Howard A. Latham
>
>
>
>
Other related posts:
