Suzanne Strasser
IOUG Webinar
April 2, 2013
How Can We Use OEM 12c to Solve the
Following Business Needs?
• Multiple production and development/test
databases, with different monitoring and alert
requirements for each group
• Production databases: generate critical alerts for
errors seen in the database alert log
• Development/test databases: generate warning alerts
only
Production
Database All Targets
OEM adds DB to group Based on lifecycle status property
Administration Administration
Group: Production Group: Test
associate associate
• EM_METRIC_VALUES
• Raw data stored at its most detailed level for 7 days
• EM_METRIC_VALUES_HOURLY
• Raw data aggregated into hourly averages
• Retained for 32 days
• EM_METRIC_VALUES_DAILY
• Hourly average data aggregated into daily averages
• Retained for 12 months
Rollup Tables and Their Retention
Settings
• Key columns:
• ENTITY_NAME – the target or component name
• COLLECTION_TIME – data collection time in the target time zone
• METRIC_GROUP_NAME – name of the metric group
• METRIC_COLUMN_NAME – name of the metric column
• KEY_PART_1 – key part 1 of composite key
• VALUE – value of metric
Where to Find the Metric Group Name
and Metric Column Name?
• Query from
gc$metric_columns
• The values of
METRIC_GROUP_LABEL
and
METRIC_COLUMN_LABEL
will match the names
displayed in OEM
Querying Metric Group and Column
Names
Raw Data Query: gc$metric_values
“Raw Data” Graph in Excel
Management Repository Views:
gc$metric_values_hourly
• Hourly averages view corresponding to the
EM_METRIC_VALUES_HOURLY table
gc$metric_values_hourly
union with
gc$metric_values
gc$metric_values_daily
union with
gc$metric_values
• suzanne.strasser@returnpath.com
• http://www.returnpath.com