RE: serial#, last_call_et for long running queries

From: Xiang Rao <xiang_rao@xxxxxxxxxxx>
To: <exriscer@xxxxxxxxx>, Alex Monte <ax.mount@xxxxxxxxx>
Date: Mon, 22 Sep 2014 10:45:50 -0400

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


Sent from my Windows Phone
________________________________
From: Ls Cheng<mailto:exriscer@xxxxxxxxx>
Sent: ‎9/‎22/‎2014 10:23 AM
To: Alex Monte<mailto:ax.mount@xxxxxxxxx>
Cc: Oracle-L Group<mailto:oracle-l@xxxxxxxxxxxxx>
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@xxxxxxxxx> 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
>
>

RE: serial#, last_call_et for long running queries

Other related posts: