Re: Enterprise Manager Performance Pages Sampling interval

Pretty sure when you’re looking at the perf tables, OEM is just reading and displaying what’s in the views in the DB. This data is not collected and stored in OEM, just pulled right out of AWR when you connect. Looking at the queries the dbsnmp user is running while you’re viewing the perf page is a good idea to see what the query is. Don’t think OEM is doing any filter/sampling of its own.

> On Dec 5, 2019, at 7:13 AM, Zwettler Markus (OIZ) <Markus.Zwettler_at_zuerich.ch> wrote:
>
> Average Active Session History comes from dba_hist_sysmetric_summary. It is based on end_time which is hourly as far as I can see.
>
> Average Active Sessions Real Times comes from v$sysmetric. It is also based on end_time which is 30 second intervals as far as I can see.
>
> Do you agree?
>
> Thanks,
> Markus
>
>
>
> On 2019/12/04 02:21, Zwettler Markus (OIZ) wrote:
>
> So, the "Average Active Sessions" page comes from v$active_session_history?
>
> At which vertex interval is the graph build on? I don't think that they use every 1 second sample as an vertex.
>
>
>
> You should be able to dig into this yourself. In EM 13.3, connect to a database target and go to Performance->Performance Hub->ASH Analytics. Once there, go to Performance->SQL->Cloud Control SQL History. This new window will show you the SQLs that the ASH Analytics page just used to pull its data.
>
> Of course, that's just the tip of the iceberg. EM13 requires a PL/SQL package to be installed for each database target. This package is OMC_ASH_VIEWER and is installed in the monitoring connection's schema. But at least it's not wrapped, so you can trip through the various procedures and functions, and that should hopefully get you what you're looking for.
>
> Hope this helps! Good luck!
>
> Rich
>

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