Entities, metrics, and lookup details for Oracle Enterprise Manager


This topic explains the predefined metrics that are provided by the Oracle Enterprise Manager (OEM) and their mapping with the BMC Helix Continuous Optimization metrics. The OEM provides metrics for entities, such as database server (entity type being generic), database instance, database cluster, and Real Application Cluster (rac), and Automatic Storage Management (ASM). 

The ETL accesses the following views to collect metrics from the Oracle Enterprise Manager (OEM):

  • MGMT$METRIC_DAILY
  • MGMT$METRIC_DETAILS
  • MGMT$METRIC_HOURLY

According to the Oracle documentation, Oracle Diagnostics Pack must be enabled to view the listed repository views.  An additional license is required to enable the Oracle Diagnostics Pack. For details, see the Oracle Enterprise Manager documentation.

Database server metrics

Important

  • The Database Server entity type has been discontinued. It will be replaced by Generic entity type.
    • Your next run of Oracle Enterprise Manager (OEM) ETL will modify existing Database Server entity types into Generic and also henceforth identify Database server entity type as Generic. This entity will be placed in the opt:meas:app:oem namespace. For more details about this, see Namespaces.
    • The same instance could, however, be extracted as a Generic or Virtual machine type by another ETL and its metrics placed in a different namespace.
    • Subsequent automatic entity reconciliation will reconcile these entities into a single entity either of Generic or Virtual machine entity type.
  • A system generated tag (Type: SERVER_TYPE; Name: DATABASE) is assigned to these database server entities to identify them among all existing entities of entity type Generic. Do not delete this tag.
    Server_type_Tag_w_EnttTyp_Generic.png


Load

Disk activity summary (DiskActivitySummary)

Disk activity (DiskActivity)

Disk activity metrics are not collected if the Alerting and Historical Trending option is not selected in the Use of Metric Data section in the OEM environment. The metrics will be available after 48 hours of enabling this option. 

To enable the Alerting and Historical Trending option
  1. Log on to the Oracle Enterprise Management database as an administrator.
  2. In the OEM interface, from the top navigation bar, click Targets > Hosts
  3. Select the required host from the list of hosts.
  4. From the top-left of the screen, click Host to see the dropdown menu.
  5. Select the Monitoring > Metric and Collection Settings option.
  6. From the Metrics tab, select the Disk Activity metric. 
  7. Click the Collection Schedule link (Example: 15 minutes) corresponding to the the Disk Activity metric.
  8. On the Edit Collection Settings: Disk Activity page, in the Use of Metric Data section, select the Alerting and Historical Trending option. 
  9. Click Continue and then OK to save the changes. 


File system (Filesystems)

Network

Paging activity (PagingActivity)

Host storage history (host_storage_history)

Database Server configuration metrics

If the MGMT$HW_CPU_DETAILS view is available in OEM, the following configuration metrics are supported.

If the MGMT$HW_CPU_DETAILS view is not available but the MGMT$OS_HW_SUMMARY view is available, the following cofiguration metrics are supported.

For the MGMT$TARGET_TYPE_PROPERTIES view, the following metrics are supported:

Database Instance (db) metrics

Database Archfull (ArchFull)

Database resource usage (Database_Resource_Usage)

Database instance efficiency (instance_efficiency)

Database instance throughput (instance_throughput)

Dump full (dumpFull)

Database size (DATABASE_SIZE)

Tablespace allocation (tbspAllocation)

Problem table space (problemTbsp)

System Global Area pool wastage (sga_pool_wastage)

Wait Bottlenecks (wait_bottlenecks)


Database instance configuration metrics

For the MGMT$TARGET_PROPERTIES view, the following metrics are supported:

Pluggable database instance metrics

Pluggable database instance configuration metrics

Pluggable database instance performance metrics

Real Application Clusters (rac) metrics

Tablespace allocation (tbspAllocation)

Problem tablespace (problemTbsp)

Service performance (service_performance)

Database size (DATABASE_SIZE)

Metrics for monitored hosts

The following configuration and performance metrics are supported for monitored hosts:

Configuration metrics for monitored hosts

  • BYBENCHMARK_DESCRIPTION
  • BYBENCHMARK_VALUE
  • CPU_FAMILY
  • CPU_MHZ
  • CPU_MODEL
  • CPU_NUM
  • DISK_SIZE
  • LCPU_NUM
  • NET_IP_ADDRESS
  • OS_FAMILY
  • OS_TYPE
  • OS_VER
  • TOTAL_REAL_MEM

Performance metrics for monitored hosts

  • CPU_RUN_QUEUE
  • CPU_UTIL
  • CPU_UTIL_SYSTEM
  • CPU_UTIL_USER
  • CPU_UTIL_WAIO
  • DISK_IO_RATE
  • MEM_ACTIVE
  • MEM_PAGE_SCAN_RATE
  • MEM_REAL_UTIL
  • MEM_SWAP_OUT_BYTE_RATE
  • MEM_UTIL
  • PROCESS_NUM_RUNNING
  • SWAP_SPACE_UTIL


Metrics for Cluster Database

The following configuration and performance metrics are supported for the cluster database and aggregated by the hosts (children of the cluster database):

Configuration metrics for cluster database

  • CPU_MHZ 
  • SW_VER
  • TOTAL_REAL_MEM

Performance metrics for cluster database

  • CPU_UTIL 
  • CPU_UTIL_SYSTEM
  • CPU_UTIL_USER
  • CPU_UTIL_WAIO
  • MEM_ACTIVE
  • MEM_REAL_UTIL
  • MEM_UTIL

Metrics for Automatic Storage Management (ASM) entities

The following configuration metrics of ASM instances and clusters are supported.

Configuration metrics for ASM instances

Configuration metrics for ASM clusters

Configuration metrics for ASM disk groups

Performance metrics for ASM disk groups

The following performance metrics for ASM disk groups are supported.

Disk Group Usage (DiskGroup_Usage)


Database Disk Group Usage (Database_DiskGroup_Usage)


Disk Group Imbalance Status (diskgroup_imbalance)

Lookup details

The OEM extractor defines multiple lookup fields. The following table lists the sequence of field set for strong and weak lookup. For more information about entity lookup, see Understanding-entity-identification-and-lookup.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*