RE: serial#, last_call_et for long running queries

From: Xiang Rao <xiang_rao_at_hotmail.com>
Date: Mon, 22 Sep 2014 10:45:50 -0400
Message-ID: <BLU405-EAS96C7387C0A5CE1EFB1A14A95B30_at_phx.gbl>

For 11gr2, column sql_exec_start of v$session can help, too.

Sent from my Windows Phone

---

From: Ls Cheng<mailto:exriscer_at_gmail.com> Sent: ‎9/‎22/‎2014 10:23 AM
To: Alex Monte<mailto:ax.mount_at_gmail.com> Cc: Oracle-L Group<mailto:oracle-l_at_freelists.org> Subject: Re: serial#, last_call_et for long running queries

hi

last_call_et isnt exact, in a long running query using NL Join whenever a row is returned the last_call_et count is reset to cero

a good query is this one but it samples ash, to look queries who have been running over 10 minutes:

select session_id, count(sql_id)

          from v$active_session_history
         where sample_time > sysdate - 605/86400

group by session_id
having count(sql_id) >= 600

On Tue, Sep 16, 2014 at 7:51 PM, amonte <ax.mount_at_gmail.com> wrote:

> 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
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Sep 22 2014 - 16:45:50 CEST