Exadata Monitoring and Management Best Practices
Exadata Monitoring and Management Best Practices
Mughees A. Minhas
Oracle
Redwood Shores, CA, USA
Keywords:
For hardware targets, you now have a photorealistic view that displays all component details,
including any open incidents. Infrastructure components are now available as new target types
which enable drill down to alerts and notifications for specific components like IB switch,
power distribution unit (PDU), Switches etc.
Critical incidents in the hardware layer can now be published to a 3rd party ticketing system
using the connector framework, something that Oracle hardware customers have asked for a
long time.
As Oracle releases new hardware and software, the Oracle Exadata plug-in is updated, tested,
and certified to accommodate the new products and 13.2 currently would support the X6-2
configuration of Exadata
The Grid and Cell home pages along with the performance pages can be used to get answers
to questions like
Many companies, especially government organizations, require root access or the SSH
service on the cells to be disabled as part the compliance requirements.
Service providers that host Exadata machines provide access to a virtual machine
running on the compute node. Customers are not allowed to ssh into the cell to
manage the cell using CellCLI.
For the use cases above, the only way to manage the cell is by using ExaCLI running on the
compute node.
Enterprise Manager 13c allows you to monitor the extreme flash only configuration that was
announced with the X5-2 configuration of exadata. One of the typical questions that
customers have is how much of flash throughput would an OLTP consume? Benchmarks at
oracle say that OLTP peak loads would consume 20% of flash throughput which means that
we can use the rest of it for scans.
EM allows us to monitor and track the throughput usage, utilization percentage from a
throughput perspective and also to monitor the latency and Flash IORM waits. This gives us
a very good visual interpretation of the workload distribution and basis which we can chose to
change your IORM strategy.
EM now allows us to monitor and track the throughput usage, utilization percentage from a
throughput perspective and also to monitor the flash latency and IORM waits in addition to
the Disk latency and IORM waits. You can also drill down to the performance page to see a
holistic view of I/O distribution across all the databases and identify the top consumers.
You could do a variety of administrative tasks like enable/disable port , clear error counters
and set up SNMP subscription which is new in 13c.
With EM 13c, there is full support for patching the entire Exadata stack, including:
Compute nodes: Firmware and operating system (OS).
The patching application offers the facility to run the pre-flight checks and monitor the logs
from a single place (imagine having to manually monitor the patch execution logs for grid
infrastructure, operating system, storage for all the compute and storage cells in a rack)
The new Consolidation Workbench provides an end-to-end workflow that provides three
distinct steps:
You can audit various important configuration settings within an Oracle Database Machine
Exadata System - Database Servers, Storage Servers and Infiniband Switches. It produces
two reports, summary and detailed. The detailed report will contain Benefit/Impact, Risk and
Action/Repair information.
With EM 13c, integration of Exacheck into the Compliance framework of Enterprise Manager
is complete; this would let you generate automated notifications and reports for any violation
the Exadata configurations. You can install setup and upgrade the exachk utility end to end
through EM.
Contact address:
Mughees Minhas
Oracle
400 Oracle Parkway
Redwood City, CA 94065
USA