Re: serial#, last_call_et for long running queries
Date: Tue, 16 Sep 2014 22:14:43 -0500
Message-ID: <CAFH+ifefFrxCE+J0=HybR4K55hzJzXkYx6M_PSr2unY7+ZH5ug_at_mail.gmail.com>
What about v$session_longops or gv$session_longops?
On Tue, Sep 16, 2014 at 9:57 PM, Chitale, Hemant K <Hemant-K.Chitale_at_sc.com> wrote:
> SERIAL# goes together with SID as the unique identifier (within the
> instance) for a session.
>
>
>
> You need to look at SEQ# to see if the Wait Event is changing.
>
>
>
> Hemant K Chitale
>
>
>
>
>
> *From:* oracle-l-bounce_at_freelists.org [mailto:
> oracle-l-bounce_at_freelists.org] *On Behalf Of *amonte
> *Sent:* Wednesday, September 17, 2014 1:51 AM
> *To:* Oracle-L Group
> *Subject:* serial#, last_call_et for long running queries
>
>
>
> Hello
>
> In order to identify long running queries I have been using last_call_et,
> if a session with a large last_call_et then it has not changed query.
>
> Is it more useful add serial#? Since serial# does not change in a long
> running query neither?
>
> Thank you
>
> Alex
>
> This email and any attachments are confidential and may also be
> privileged. If you are not the intended recipient, please delete all copies
> and notify the sender immediately. You may wish to refer to the
> incorporation details of Standard Chartered PLC, Standard Chartered Bank
> and their subsidiaries at https://www.sc.com/en/incorporation-details.html
> .
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Sep 17 2014 - 05:14:43 CEST