Is it possible to detect long-running transactions?

We would like to automatically catch the cases where some
(for example) makes a change with Sql Developer, forgets
to commit, and then leaves for the evening.

tia!
Mark

--
Mark Harrison
Pixar Animation Studios

<mh (AT) pixar (DOT) com> a écrit dans le message de news: UPmPl.16668$pr6.3562 (AT) flpi149 (DOT) ffdc.sbc.com...
v$transaction.start_time

Regards
Michel

On May 16, 2:40*am, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
Besides sessions holding locks visible in v$transaction you may also
want to consider killing sessions that are inactive for too long a
period of time. See v$session.last_call_et > n and status =
'INACTIVE'.

HTH -- Mark D Powell --

On May 15, 4:23*pm, m... (AT) pixar (DOT) com wrote:
Actually, I've seen fairly common situations where they don't forget
anything, but simply remaining connected results in ORA-1555 errors
for other people. So I just keep a log of who's on when no one should
be (OS based, since there are non-Oracle things), and kill 'em all.
Of course, I actually have a time when no one should be, and I have to
have an exception procedure for some things that actually do take way
too long, so I consider this kind of thing site-dependent, with Mark
Powell's answer perhaps the better. Maybe combined with Michel's,
since I do see a few runaways. Generalizing is difficult enough, I've
left it at "you die unless you tell me why I shouldn't kill you." My
own stuff excepted, of course :-)

jg
--
@home.com is bogus.
http://www.techflash.com/microsoft/J... gic_wand.html

mh (AT) pixar (DOT) com wrote:
"forgets to commit" would not be a long running transaction.
That would be an inactive session (possibly with outstanding locks)
--

Regards,
Frank van Bortel