Re: detecting long-running transactions?
From: Mark D Powell <Mark.Powell_at_eds.com>
Date: Mon, 18 May 2009 06:27:51 -0700 (PDT)
Message-ID: <91cabef7-a906-47d9-8d3d-66a7fdc34eb6_at_n21g2000vba.googlegroups.com>
On May 16, 2:40 am, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
> <m..._at_pixar.com> a écrit dans le message de news: UPmPl.16668$pr6.3..._at_flpi149.ffdc.sbc.com...
> | 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
>
> v$transaction.start_time
>
> Regards
> Michel
Date: Mon, 18 May 2009 06:27:51 -0700 (PDT)
Message-ID: <91cabef7-a906-47d9-8d3d-66a7fdc34eb6_at_n21g2000vba.googlegroups.com>
On May 16, 2:40 am, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
> <m..._at_pixar.com> a écrit dans le message de news: UPmPl.16668$pr6.3..._at_flpi149.ffdc.sbc.com...
> | 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
>
> v$transaction.start_time
>
> Regards
> Michel
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 -- Received on Mon May 18 2009 - 08:27:51 CDT