Enterprise Manager for Engineered Systems Features

Exadata monitoring and management

Exadata target topology with alerting and incidents

Exadata Database Machine management simplifies monitoring and management tasks by integrating all hardware and software components into one entity. You do not need to individually monitor each target. Instead, you can view the whole Exadata Database Machine as a single target. You can view all critical issues in the system, monitor performance, and drill down to individual targets from the Exadata Database Machine target homepage.

Use the Topology page to view the topology of the system by cluster or by database. Clusters are a complete software system starting with a Real Application Clusters (RAC) database, the underlying Automatic Storage Management (ASM), and Cluster Ready Services (CRS). Clusters define one logical entity that is interconnected. The Database Machine could include several clusters, one cluster, or could just be a number of individual databases. While hardware racks define the hardware topology of Exadata Database Machine, clusters define the logical or system topology of Exadata Database Machine.

You can view the topology by cluster or database. Click an element in the topology and view alert data associated with the element.

Exadata storage grid performance and health

Exadata storage grid performance and health provides details on your storage system and how it is used. There are different sections showing the most important information on your storage grid.

• Overview: Provides details of Exadata storage server availability status, health details, I/O resource manager status, and server version.

• Performance: Provides hard drive and flash response time to IO requests, number of I/Os in the queue and average per-disk type.

• Capacity: Provides capacity details of different storage types available on the storage server.

  • Total available capacity of hard drive and flash.
  • Flash cache space information about keep objects, non-keep objects, and unused space. This section also provides information about the size of the flash used for logging.
  • Capacity information for ASM disk groups.

• I/O activity: Provides performance information, such as utilization, latency, and throughput for available storage drives. This section also provides flash cache read/write, Smart Scan I/O throughput, InfiniBand network throughput, Smart Log efficiency, and IORM boost.

• I/O distribution by database: Displays information about databases that are ranked top five in I/O utilization for the available storage drives. Other is an aggregation of remaining databases. This section also displays the hard drive I/O service time and flash I/O service time for top five databases and other databases.

• Incidents and problems: Lists alerts for the target.

IORM monitoring and management

The I/O Resource Management (IORM) feature allows you to manage how multiple databases share the I/O resources of an Oracle Exadata Cloud VM cluster for systems using the new resource model or database system.

Enterprise Manager allows you to monitor how both the hard disk and flash disk I/O throttles individual databases. The monitoring is in near real time, and it is possible to drill down to affected databases and see which statements are affected.

I/O Resource Manager settings lets you view and update the IORM configuration of Exadata storage server.

Database Resource Management (DBRM) settings display the list of databases and their basic configuration that are using Exadata storage server resources. Here, you can launch the database resource management page.

Since monitoring is in near real time it will be possible to see how changes will affect databases on the Exadata systems.

Database I/O distribution

IORM monitoring provides a view of the performance statistics of disk I/O. These statistics help to identify which databases and consumer groups are using the available resources. They also help to adjust the IORM configuration as needed.

Exadata Autonomous Health Framework (AHF) administration

The AHF administration feature provides functionality to manage AHF and EXAcheck on a single or a multiple Exadata machines. It provides out-of-the-box installation, upgrade, and auto-upgrade of AHF on all nodes. It provides version control, upgrade status, and history to make sure all nodes can execute the latest compliance and security checks when an EXAchk is requested.

Exadata infrastructure patching

Exadata infrastructure patching is a fleet-level patching of multiple components. Download the Exadata software, create standard gold images for individual components, and you are ready to patch your Exadata infrastructure.

Enterprise Manager Fleet Maintenance allows you to schedule patching of multiple Exadata machines in parallel to minimize the maintenance window.

Patching of components on an individual Exadata machine is done in a rolling fashion to reduce or eliminate downtime. It provides the ability to perform post validations and even rollback to a previous release if necessary.

Exadata dashboards

Exadata dashboards help you understand configuration and capacity from fleet level down to individual components. Now you can perform proper capacity planning and simplify hardware refresh.

With the ability to filter and group on properties such as hardware generation, lifecycle status, location, and more, it’s easy to find out where there is available capacity and how much. The configuration view and filtering capabilities allow you to identify and remediate hardware and software that may need attention, such as a software release with a security alert.

Zero Data Loss Recovery Appliance monitoring and management

Zero Data Loss Recovery Appliance performance monitoring

The Zero Data Loss Recovery Appliance homepage lists any existing warnings and alerts as well as the following information:

• A summary that shows the number of databases with alerts, warnings, or no issues. In Cloud Control, an alert indicates a particular metric condition, for example, that a metric threshold has been reached.
• Performance statistics can be monitored for the following metrics:
  • Backup data sent to the Recovery Appliance over the network
  • Restore data received from the Recovery Appliance over the network
  • Recovery Appliance ASM disk group read or write I/O
  • Recovery Appliance container file read or write I/O
  • Recovery Appliance container file allocation rate
• The Media Managers and Replication information show the status of copy-to-tape and Recovery Appliance replication services.
• Protected Database Issues summarizes the backup status for protected databases, and provides a category filter so you can view which databases are affected.
• Incidents and Events displays incidents and events reported for Recovery Appliance and all associated targets. You can filter by target and category. You can click the Summary link to drill down to the Incident Manager to view detailed information about the incident.

Protection policies management

The Create Protection Policy page in Oracle Enterprise Manager Cloud Control is the recommended interface for creating protection policies.

A protection policy is a named, logical object recorded in the Recovery Appliance metadata database. To be added to a Recovery Appliance, a protected database must be associated with a specific protection policy. The default protection policies are Platinum, Gold, Silver, and Bronze.

Each protection policy specifies different values for the disk and tape recovery windows. These values apply to every database protected by the policy.

The protection policy management in Enterprise Manager supports the following.

• Setup and configuration
  • Create protection policies for each database tier
• Ongoing maintenance
  • Update the attributes of a protection policy
  • Delete a protection policy

Protected database management

The Protected Databases page in Oracle Enterprise Manager Cloud Control is the recommended interface for starting the database enrollment process.

The Protected Databases page lists all databases under the management of the Zero Data Loss Recovery Appliance, whether they back up directly to the Recovery Appliance or are configured for downstream (Recovery Appliance replication). You can add protected databases by selecting an individual database, multiple databases, or a previously defined Enterprise Manager group.

Configuring protected database access in Enterprise Manager supports the following:

• Setup and configuration
  • Create virtual private catalog accounts
  • Enroll the protected database with the Recovery Appliance
• Ongoing maintenance
  • Update the properties of an existing protected database
  • Remove metadata for protected databases from the Recovery Appliance
  • Revoke access to a specific protected database from a specific virtual private catalog owner

Database fleet backup configuration

Database fleet backup configuration provides the ability to automate all steps in the backup configuration process. Every step for host configuration, database configuration, and Data Guard configuration is automated.

You can automatically configure one or a set of databases as soon as they join a group in Enterprise Manager.

Database fleet backup scheduling

The database fleet backup scheduling provides the ability to automate backup scheduling for databases. You can automatically schedule backups for one or a set of databases as soon as they join a group in Enterprise Manager.

Zero Data Loss Recovery Appliance protected database fleet archival backup scheduling

Recovery Appliance protected database archival backup is a Recovery Appliance feature that creates a point-in-time archival backup to tape or object store directly from the Recovery Appliance instead of the database. This will offload the database from additional backups.

Enterprise Manager provides a new feature that allows administrators to schedule these backups for a database or a group of databases. It is possible to assign the database to a protection policy, and archival backups are scheduled according to that protection policy.