Re: V$active session history
From: Jeremy Schneider <jeremy.schneider_at_ardentperf.com>
Date: Thu, 19 Mar 2015 14:05:06 -0400
Message-ID: <CA+fnDAadBc3EdevLGOhaWCmRQ_UwcpBRPnfJ+EiuAe1FmnNVCA_at_mail.gmail.com>
you probably already checked this, but maybe min(sample_time) would show if it already cycled out of the memory buffer? if that was the case then you'd need to look at the dba_hist_* view instead?
Date: Thu, 19 Mar 2015 14:05:06 -0400
Message-ID: <CA+fnDAadBc3EdevLGOhaWCmRQ_UwcpBRPnfJ+EiuAe1FmnNVCA_at_mail.gmail.com>
you probably already checked this, but maybe min(sample_time) would show if it already cycled out of the memory buffer? if that was the case then you'd need to look at the dba_hist_* view instead?
every SQL that runs for more than 1 second will show up in v$active_session_history (until the memory buffer cycles around). every SQL that runs for more than 10 seconds will be retained in the dba_hist_* view.
-J
-- http://about.me/jeremy_schneider On Wed, Mar 18, 2015 at 12:57 PM, Mohamed Houri <mohamed.houri_at_gmail.com> wrote:Received on Thu Mar 19 2015 - 19:05:06 CET
> Dears
> This morning i was monitoring an insert/select using sql monitor in
> 11.2.0.3. The insert was busy reading a unique index 3 millions times
> showing cpu and db file sequential read at this particular line. Tanel poder
> snapper shows that the correspinding sql_id id on cpu and db file sequential
> read. But gv$active_session_history shows no rows for the same moment
> Is it because each unique index scan takes less than 1 sec that it is not
> stored in gv$active_session_history?
> Thanks
-- http://www.freelists.org/webpage/oracle-l