Académique Documents
Professionnel Documents
Culture Documents
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Program Agenda
1
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
October 2015
Monitoring complexity is increased if the Exadata platform is used to house databases for
multiple LOBs and the Exadata infrastructure is maintained by a yet another team.
7
The Exadata plugin displays all components of the Appliance Components. Some examples:
The Exadata cell information is a component that the Application DBA team wanted access to.
This required additional group and incident rule setup.
8
The 12c target type oracle_dbmachine is a composite target that includes ALL targets within the Exadata
environment.
10
How Wellsfargo handles this unique separation of duty and alert notifications
Create a separate 12c group for those Exadata targets that the LOB teams will have access to. This includes the
Exadata Storage Server Grid and the Exadata Storage Servers
Place the databases that each LOB and Exadata support teams are responsible for in groups that each team has full
control over.
Create 12c Roles that contain the appropriate groups for each support team
11
Notice both groups appear to have the same targets. However group 2 only contains:
There is an automatic expansion of the DB Machine targets. If the DB Machines are added
to an Incident Rule, ALL targets on the DB Machine will be included.
12
There are Incident rules for Exadata targets in one rule set, AND
a specific DB Machine Ruleset.
13
The two Exadata rules for the Exadata Support team used two different groups:
14
The typical setup for LOB support groups (Those supporting DBs on Exadata) required view access into the
Exadata Cells
A second LOB group was needed because view access is given to the cell targets. The
main LOB group propagates full for all targets included.
15
The LOB Exadata group is only given View access to the cells.
The role these groups are in get assigned to the DBAs in that LOB.
e.g. View Role: LENDING_CORE_ROLE
16
The LOB rules also include a specific rule for cells monitoring.
17
The Exadata Plugin gives a detailed look into the setup and health of an Exadata environment. However, care
must be taken to secure and authorize only those targets that are required for each support role.
The ability to limit LOB DBA access to those targets they are responsible for.
The ability to produce alerts for LOB DBAs that exclude specific platform hardware targets that are the sole
responsibility of the Exadata support team.
Giving the LOB DBA team a view into the Exadata cells, and allow them to receive alerts for the cells.
The ability to alert on the DB Machine target without inundating the Exadata support team with database alerts
that should only be sent to the LOB DBA teams.
Allow the Exadata support team to receive alerts for databases they are responsible for (such as fsdb).
18
New incident rules were created with all out of the box metrics that Oracle defined
thresholds for.
19
The Exadata Plugin also exposes additional metrics that cannot be used directly for alerting
There are metrics that are collected from the Exadata environment, that thresholds cannot be
set for.
20
In cases where metrics are exposed, but not available for alerting, Repository side Metrics extensions can be
used to produce alerts on those metrics that have not be defined with thresholds.
Application LOB teams desired additional cell alerting that was not available out of the box,
but that could be exposed via Metric Extensions.
21
Using Repository side Metric Extensions the desired metrics can be alerted on:
Custom repository side Metric Extensions were created and then added to the LOB DBA
Incident Rules.
22
Repository side Metric Extensions use the metric data that is populated when the Exadata Plugin is deployed:
The Repository side Metric Extensions used data that is being captured by the Exadata
Plugin.
23
Summary:
The Exadata Plugin provides the 12c functionality needed to See into and monitor your Appliance.
The plugin provides an extensive picture of what your Exadata environment looks like. Providing an easy to
understand landscape of all involved components.
Performance data for all Exadata components is available either through the GUI or 12c reporting.
Monitoring and alerting for all Exadata Target Types can be enabled to ensure stability and reduce risk of
outages.
12c allows for very specific Exadata target security for a variety of support roles.
12c Exadata monitoring can easily be extend with Metric Extension to enhance alerting capabilities.
24
Om Prakash Seth
Vice President - IT
omprakash.seth@hdfcbank.com
Extreme
Performance
High
Availability
Purpose Built
Engineered
Machines
Scalability
Technology
Management
3 full Rack & 5 half Rack Oracle Super cluster being deployed
across 3 data centers in HA for running Core Retail Banking
System
Performance
Optimization & Advisory
Managing
DB
operations
Performance &
Availability
Management
Standardization&
Compliance
Cloud Ready
Architecture
Thank You
omprakash.seth@hdfcbank.com
34
Oracle Confidential Internal