Re: V$active session history
From: Ryan January <rjanuary_at_gmail.com>
Date: Thu, 19 Mar 2015 13:11:56 -0500
Message-Id: <890CD206-B68E-4A13-84E8-231B7B478139_at_gmail.com>
I agree with Jeremy, but have a slight correction. As I understand it, every 10th ASH sample will make it to the dba_hist* views. A sql statement wouldn't have to be active a full 10 seconds to be included. That session can sit idle for 9.999 seconds and, by being active at just the right time, be included in the AWR sample.
Date: Thu, 19 Mar 2015 13:11:56 -0500
Message-Id: <890CD206-B68E-4A13-84E8-231B7B478139_at_gmail.com>
I agree with Jeremy, but have a slight correction. As I understand it, every 10th ASH sample will make it to the dba_hist* views. A sql statement wouldn't have to be active a full 10 seconds to be included. That session can sit idle for 9.999 seconds and, by being active at just the right time, be included in the AWR sample.
> On Mar 19, 2015, at 1:05 PM, Jeremy Schneider <jeremy.schneider_at_ardentperf.com> wrote:
>
> 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.
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Mar 19 2015 - 19:11:56 CET