Правильный Вася,

Есть вот такой вот документ - DBA_HIST_SYSMETRIC_HISTORY Does Not Capture All Metrics (Doc ID 2724352.1)

На случай если не доступа
SYMPTOMS

A query on view DBA_HIST_SYSMETRIC_HISTORY does not show all metrics shown in V$SYSMETRIC_HISTORY:
SQL> select count(0), METRIC_NAME from DBA_HIST_SYSMETRIC_HISTORY group by METRIC_NAME order by 1;
23 rows selected.
SQL> select count(0), METRIC_NAME from V$SYSMETRIC_HISTORY group by METRIC_NAME order by 1;
161 rows selected.

CAUSE

This is expected behavior as documented in internal bug discussion.
The view DBA_HIST_SYSMETRIC_HISTORY will only display a few default metrics from V$SYSMETRIC_HISTORY. Not all metrics will be displayed in this view.
Additional metrics can be populated when user created Threshold-based Server Generated Alerts are generated on the metric.
However, even if the thresholds have been defined, DBA_HIST_SYSMETRIC_HISTORY will only be populated if the thresholds are violated and alerts are issued to EM.
Metric Thresholds can be set either via Enterprise Manager or via DBMS_SERVER_ALERT.SET_THRESHOLD() API.