Re: detecting long-running transactions?
From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Fri, 22 May 2009 10:50:42 +0200
Message-ID: <1fc42$4a166763$524b9d64$15010_at_cache1.tilbu1.nb.home.nl>
mh_at_pixar.com wrote:
> 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
>
Date: Fri, 22 May 2009 10:50:42 +0200
Message-ID: <1fc42$4a166763$524b9d64$15010_at_cache1.tilbu1.nb.home.nl>
mh_at_pixar.com wrote:
> 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
>
"forgets to commit" would not be a long running transaction. That would be an inactive session (possibly with outstanding locks)
-- Regards, Frank van BortelReceived on Fri May 22 2009 - 03:50:42 CDT