Oracle Exadata Database Machine Administration

5 Oracle Exadata Database Machine Administration

This chapter provides the information needed to administer your Oracle Exadata Database Machine through Oracle Enterprise Manager Cloud Control 13c. The following topics are discussed:

Creating Roles to Manage the Plug-in

To manage the plug-in, you need to create roles and administrators, and then assign roles to administrators. This restricts the privileges that each user has, for example in deleting the plug-in or accessing reports.

Note:

For security reasons, Oracle recommends that the SYSMAN account be used only as a template to create other accounts, and not used directly.

To manage the plug-ins, you must have the Self Update privileges. See Assigning Self Update Privileges to Users in Cloud Administration Guide. For information on creating custom roles, see Creating Custom Roles for Self Service Application Administrators and Users in Cloud Administration Guide.

To create roles to provide management rights to users:

Log in to the Enterprise Manager Cloud Control as the super administrator user.
Click Setup, then Security.
Select Roles.

On the Security page, a list of predefined roles is provided. These roles can serve as basis to define custom roles to suite specific site level requirements.

Note:

The predefined roles provided cannot be edited or deleted.
Select a role that closely matches the role you wish to create. Click Create Like.
On the Properties page, enter a name for the role you wish to create. You can optionally add a description.

Click Next.
On the Roles page, select the roles from the list of Available Roles. Click Move to add the role to Selected Roles.

Click Next.
On the Target Privileges page, select the privilege you want to grant to the new role.

Click Next.
On the Resource Privileges page, you can edit specific privileges to be explicitly granted. Click the Manage Privilege Grant edit icon to make the changes.

Click Next.
On the Administrators page, select the administrators from the list of Available Administrators that you want to grant the new role to. Click Move to add the administrator to Selected Administrators.

Click Next.
On the Review page, a complete summary of the new role you have created is displayed. Click Back to go to previous screens to make changes. Click Finish to complete the role creation.

When the newly created administrator logs in, unlike SYSMAN, the administrator is restricted by the privileges set.

Exadata Database Machine Topology

Database Machine management simplifies monitoring and managing tasks by integrating all hardware and software components into one entity. You do not need to monitor each target individually, but 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 Database Machine target home page.

The following topology topics are presented in this section:

Use the Topology page of Database Machine to view the topology of the system by Cluster or by Database. Clusters are a complete software system starting with a RAC database, the underlying ASM, and 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 the Database Machine, clusters define the logical or system topology of the 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.

You can monitor all components of the Database Machine. Database Machine monitors all subcomponent targets, whether hardware or software. This includes the database, ASM, CRS, hosts, Exadata and the InfiniBand network.

To view the topology of an existing Database Machine target:

From the Targets menu, select Exadata.

Enterprise Manager displays the Oracle Exadata Database Machines and Cloud Services page showing all the available Exadata targets. From this page, you can add hardware components (such as Oracle Exadata Storage Servers, InfiniBand switches, Ethernet Switches, KVM switches, PDU, and compute node ILOM) in the Oracle Database Machine as managed targets.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target whose topology you want to view.
From the Oracle Database Machine Home page, click the Database Machine menu, then select Members and then Topology from the drop-down menu.

Enterprise Manager Cloud Control displays the Configuration Topology page.

Drilling Down to Individual Targets of Database Machine

You can drill down immediately to a subcomponent target of the Database Machine (such as RAC, a database instance, or an Exadata Storage Server).

To drill down to individual targets:

From the Targets menu, select Exadata.

Enterprise Manager displays the Oracle Exadata Database Machines and Cloud Services page showing all the available Exadata targets.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target whose components you want to view.

Enterprise Manager displays the Oracle Database Machine Home page showing an Overview, Schematic, and Incident section for the selected Database Machine.
From the Oracle Database Machine Home page, use the left navigation panel to expand the list of available targets that comprise the Database Machine.
Click the target to which you want to drill down.

Viewing Virtual Exadata Targets

Once discovered, the Exadata plug-in shows the virtual machines monitored by Enterprise Manager Cloud Control:

Note:

The schematic diagram in the Database Machine home page is based on the content of the databasemachine.xml file found during discovery. The virtual platforms (Dom0) are displayed as compute nodes in the rack in the schematic diagram.

The Database Machine Software topology diagram will not display the physical Oracle Server, virtual Oracle Server targets (DomU), and Virtual Platform target (Dom0) targets. However, it will continue to show the host targets which are running in DomU.

The Software tab for the Exadata Database Machine target shows all clusters, ASM, and Database targets in the whole physical Database Machine grouped by clusters:

Viewing Critical Hardware Information for the Database Machine

You can view critical metrics for all the hardware subcomponents of the Database Machine such as DB hosts, Exadata Storage Servers, InfiniBand switches and so on. These metrics vary for different component targets. For example, database server nodes and Exadata servers include the CPU, I/O, and storage metrics.

To view critical hardware-centric information for the entire Database machine:

From the Targets menu, select Exadata.

Enterprise Manager displays the Oracle Exadata Database Machines and Cloud Services page showing all the available Exadata targets.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target whose hardware information you want to view.
From the Oracle Database Machine Home page, view the hardware schematic of the Database Machine.

Viewing Exadata Resource Utilization

Access the utilization graphs of compute and storage resources for cluster placement, database placement, database CPU utilization, database memory utilization, database I/O utilization, and disk group space allocation. From the Oracle Exadata Database Machine home page, select the type of resources and view the graphs accordingly.

Compute Resources

From Oracle Exadata Database Machine home page, click the Database Machine drop down > select Resource Utilization > click Compute Resources.

The following compute resource allocation graphs are available in virtualized Exadata. These graphs are dependent on the virtual machine hierarchy and metric data from the VI plug-in:

Cluster Placement

This graph shows the ClusterWare cluster placement on physical servers in a particular Exadata Database Machine rack. Since this is a placement graph, the widths of the data series reflect the number of clusters on the physical server that has the most number of clusters.

Database Placement

This graph shows the database placement on physical servers in a particular Exadata Database Machine rack for a particular DB cluster. Since this is a placement graph, the widths of the data series reflect the number of DB on the physical server that has the most number of databases for a particular DB cluster.

Database CPU Utilization

This graph shows the database CPU utilization per database per VM host for a particular DB cluster.

Database Memory Utilization

This graph shows the database memory utilization per database per VM host for a particular DB cluster.

Storage Resources

From Oracle Exadata Database Machine home page, click the Database Machine drop down > select Resource Utilization > click Storage Resources.

The following storage resource allocation graphs are available in virtualized Exadata for Exadata Storage Servers and Exadata Storage Server Grid:

Exadata Storage Servers

Exadata Storage Server home page has the following sections that provide graphs and detailed information about status and performance of the target:

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/O’s in the queue averaged 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, 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 like Utilization, Latency, and Throughput for that available storage drives. This section also provides Flash Cache read and 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 5 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 5 databases and other databases.
Incidents and Problems: Lists alerts for the target

Database I/O Utilization

The Database I/O utilization graph shows the database I/O utilization per Exadata Storage Server of this Exadata Database Machine.

To access the Database I/O Utilization graph, from the Exadata Storage Servers home page, go to the section I/O Distribution by Databases > click I/O Distribution for All Databases.

I/O Distribution by Databases:

I/O Distribution for All Databases - Graphic View:

I/O Distribution for All Databases - Tabular View:

Workload Distribution by Databases

The Workload Distribution by Databases graphs show database workload performance on the hard drive and flash and the flash cache space usage.

To access the Workload Distribution by Databases graphs, from the Exadata Storage Servers home page, go to the section I/O Distribution by Databases > click IORM Settings.

To access the Flash Cache Space Usage graph, click the Flash Cache Space Usage tab.

Flash Cache Space Usage:

To view the graphs that correspond to the performance of hard drives and Flash, click the Performance tab.

This section provides database workload performance on Hard Drive and Flash. You can filter databases based on their workload performance rankings. You can view the graphs for the filters like top 5 databases, rank based pagination, or a specific database. You can drill down from database workload performance monitoring to pluggable database and consumer groups. Following are some of the example graphs:

IORM Wait Time for All Databases (Hard Drive and Flash Drive):

I/O Utilization and Average small I/O response time for All Databases (Hard Drive and Flash Drive):

Exadata Storage Server Grid

Exadata Storage Server Grid home page displays the aggregated status and performance data for all the Exadata Storage Servers. The sections are similar to those that are listed for individual Exadata Storage Server targets.

An example Exadata Storage Server Grid home page:

In the Capacity section of the Exadata Storage Server Grid home page, the ASM disk group capacity is displayed for the selected cluster.

You can view the I/O Utilization graph and Workload Distribution of Databases graph by clicking on the links I/O Distribution for All Databases and IORM Settings in the section I/O Distribution by Databases. The graphs that are displayed are the aggregated information from the Exadata Storage Server member targets of the grid. For details of the graphs, see Database I/O Utilization and Workload Distribution by Databases.

Viewing Database Machine Alerts

You can view alerts on the Database Machine and drill down to details about each alert. These alerts may be performance/configuration metrics or hardware faults.

To view Database Machine alerts:

From the Targets menu, select Exadata.

Enterprise Manager displays the Oracle Exadata Database Machines and Cloud Services page showing all the available Exadata targets.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target whose machine configuration information you want to view.

Enterprise Manager displays the Oracle Database Machine home page on which you can see all alerts associated with the current DB Machine.

Viewing Metrics

Metrics can be viewed at the component level of Exadata Database Machine. To view the Exadata Storage Server metrics:

Navigate to the Oracle Exadata Storage Server home page by choosing the Oracle Exadata Storage Server target type from the All Targets page of Enterprise Manager.

Enterprise Manager displays the Exadata Storage Server Home page for the target you selected.
From the Exadata Storage Server drop-down menu, choose Monitoring and then All Metrics.

The All Metrics page allows you to view a wide variety of Exadata metrics. For a complete description of the Exadata metrics available, see the Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual.

Adding Exadata Database Machine Components Manually

You can add Exadata Database Machine components manually using the following steps:

From the Setup menu, select Add Target, then select Add Targets Manually.

Enterprise Manager displays the Add Targets Manually page where you can choose the type of target you want to add.
From the Add Targets Manually section, choose Add Using Guided Process.
From the Add Using Guided Process box, choose Oracle Exadata Database Machine and click Add.
From the Oracle Exadata Database Machine Discovery page, click on the option Discover newly added hardware components in an existing Database machine as targets. From the Select a Database Machine drop down list, select the Database Machine that has the new components and then click Discover Targets.
Choose the monitoring agent using the search option.
Provide the proper Infiniband Switch Credentials and click Next.
A prerequisite check is run. Click Next.
A list of available components for this Database Machine will be displayed. Select the new component(s) that need to be added and click Next.
Select the monitoring agent and backup monitoring agent for the new component(s).
On the Credentials page, set the credentials for the new components and click Next.
On the Review page, review all of the information and then click Submit.

Removing an Exadata Database Machine Target

To remove an Exadata Database Machine target, you can

Remove all members of the Oracle Exadata Database Machine. If the member target is shared with another Database Machine target, then the member target will not be deleted and will continue to be monitored. In other words, the member targets will be deleted if they are associated with only this Database Machine target.
Remove only system members of the Oracle Exadata Database Machine. The other member targets will not be deleted and will continue to be monitored. They can be associated to another Oracle Exadata Database Machine, if required.

Note:

You must remove the SNMP configuration on the InfiniBand switch, ILOM, Cisco switches (RoCE and Admin), and PDU manually if you remove these targets from Enterprise Manager.

SNMP unsubscription is performed automatically for the targets like Oracle Exadata Storage Servers and Oracle Exadata Compute Nodes based on the options selected.

To remove an Exadata Database Machine target:

From the Database Machine target menu, select Target Setup, then select Remove Target.
On the Remove page, select whether to remove all members or to remove only the system members.

If you choose to remove all members, then you also have an additional option to unsubscribe SNMP subscriptions for member Oracle Exadata Storage Servers and Oracle Exadata Compute Nodes. Specify the appropriate user credentials to unsubscribe the SNMP subscriptions.
Click Yes to initiate the remove job.

Note:

Host targets for the compute nodes and any targets that are also member targets of another Oracle Exadata Database Machine target will not be removed. System and non-system targets include:

System Targets:

Oracle Exadata Database Machine
Oracle Infiniband Fabric (Enterprise Manager 13c target)
Oracle Exadata Storage Server Grid

Non-System Targets:

Oracle Exadata Storage Server
Oracle Exadata KVM
Systems Infrastructure Switch
Systems Infrastructure PDU
Systems Infrastructure Rack
Oracle Infiniband Switch (Enterprise Manager 13c target)
Oracle Engineered System Cisco Switch (Enterprise Manager 13c target)
Oracle Engineered System PDU (Enterprise Manager 13c target)
Oracle Engineered System ILOM Server (Enterprise Manager 13c target)

Removing a Component of a Database Machine Target

If you need to remove a component of an Exadata Database Machine target, you can perform this task within Enterprise Manager Cloud Control 13c:

From the Database Machine home page's Target Navigation pane, right-click on the target item you wish to remove.
Select Target Setup, then Remove Target.
A warning page will display to confirm the target deletion. Click Yes to continue.

Updating the Exadata Database Machine Schematic Diagram

The schematic diagram illustrates the placement and status of the components of the Exadata Database Machine.

In some cases, the Exadata Database Machine schematic diagram is not displaying the components correctly. For example:

You may have successfully discovered the Exadata Database Machine, but some components are not displaying correctly in the Exadata schematic diagram. Instead, an empty slot is shown in place of the component.
The Exadata Database Machine schematic diagram shows the status of the component as "red/down" where as individual components would really show that they are up and running fine.
You want to re-locate or rearrange the order of the components in the slots of Exadata Database Machine schematic diagram.

To accomplish these tasks, you will need to drop a component from the schematic diagram and add the correct one:

Drop a Component from the Exadata Database Machine Schematic Diagram

To drop a component from the Exadata Database Machine schematic diagram:

From the Targets menu, select Exadata.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target that you want to modify.

Enterprise Manager displays the Oracle Exadata Database Machine home page of the selected Database Machine.
On the Exadata Database Machine schematic diagram right click on the component you wish to remove, click Remove Target.
Ensure you have selected the correct component in pop-up dialog box and click OK.
The Exadata Database Machine schematic diagram will refresh to show the empty slot.

Add Components to the Exadata Database Machine Schematic Diagram

To add a component from the Exadata Database Machine schematic diagram:

From the Targets menu, select Exadata.
From the Oracle Exadata Database Machines and Cloud Services page, select the Oracle Database Machine target you want to modify.

Enterprise Manager displays the Oracle Database Machine home page of the selected Database Machine.
On the Exadata Database Machine schematic diagram, select the Photo-Realistic view option.
Right-click on an empty slot of the photo-realistic diagram to display option the Place Target. A pop-up window Place Target into Rack is displayed. In the pop-up window, select the target to place it in the rack.
Once you see the component added in the slot you specify, click Done on the Exadata Database Machine schematic diagram.

Provisioning Virtualized Exadata Clusters

Provisioning involves repeatable, reliable, automated, unattended, and scheduled mass deployment of a RAC Cluster including virtual machines (VMs), Oracle Database (DB), Grid Infrastructure, and ASM on Virtualized Exadata.

Note:

Exadata Virtualized Provisioning is only available for virtual Exadata configured with InfiniBand networking.

The Exadata plug-in's virtualization provisioning functionality provides the following capabilities:

Creating a Database Cluster

To create a database cluster, select the servers on which you want to create the virtual machines (VM), and select the Exadata Storage servers that can be used by the virtual machines. Provide additional information like the credentials to access them, VM definition, software locations, operating system users and groups, and networking information to complete the setup.

From the Database Machine target menu, select Provisioning, then select Create Cluster.

The Exadata Provisioning Wizard will be displayed.
On the Exadata Provisioning: Cluster page, provide the information for:
- Cluster Definition: Create a cluster name. Click Show existing clusters to display a list of database clusters already provisioned.
- Virtual Machine Location: Select the servers on which you want to create the virtual machines. Select one or more from the Available Servers pane, then click the move button to move the selected server to the Selected Servers pane:
- Storage Definition: Select the Exadata Storage Servers to be used by the virtual machines. Select one or more from the Available Storage Servers pane, then click the move button to move the selected server to the Selected Storage Servers pane:
Click Next.
On the Credentials page, set the credentials for:
- Compute Server: Set the credentials for the root user. From the Set Credentials drop-down, select All to apply the settings to all servers, or select one or more servers from the list and select Selected to apply the settings to only the selected servers.
  
  In the Set Server Credential pop-up window, select an existing named credential or select New to create a new one.
  
  Click Test Connection to verify that the credentials are properly set. If successful, the Test Credential Status will update to show Succeeded.
- Exadata Storage Server: Set the credentials for the Exadata Storage Server administrator.
  
  In the Set Server Credential pop-up window, select an existing named credential or select New to create a new one.
  
  Click Test Connection to verify that the credentials are properly set. If successful, the Test Credential Status will update to show Succeeded.
- Agent: If Exadata Storage Server is monitored using RESTful API, then you must provide the agent host users and passwords for all the agents. From the Set Credentials drop-down, select an existing named credential or select New to create a new one.
  
  Click Test Connection to verify that the credentials are properly set. If successful, the Test Credential Status will update to show Succeeded.
Click Next to define the Virtual Machines.
On the Virtual Machines (VMs) page, provide the following information:
Note:

When available, the Exadata Provisioning Wizard will pre-populate the fields with the appropriate defaults. You can change this information to suit your environment.
- Virtual Machine Definition: In this region, provide the details to define the VM:
  - Virtual Machine Size: Select Small, Medium, or Large. Click Customize to adjust the number of CPU cores and available memory.
  - Root password: Create a password in the two password fields.
  - Verify the Prefix, DNS, and NTP fields.
  - Time Zone: select the appropriate time zone from the drop-down list.
- Software Locations: When available, the Exadata Provisioning Wizard will pre-populate the fields; otherwise, provide the following information:
  - Inventory Location
  - Grid Infrastructure Home
  - Database Home Location
  - Agent Installation Base Directory
  - Agent Port (optional)
  - Software Language (optional)
- Operating System Users and Groups: Like the Software Location region, the Exadata Provisioning Wizard will pre-populate the fields except for the password fields. Otherwise, provide the following information:
  - User name: including the ID, password, and home directory.
  - DBA group name and ID.
  - OINSTALL group name and ID.
Click Next to provide the Network details.
On the Network page, specify the IP address, name and domain used for the Admin, Client and Private network. Provide the details for the following information:
- Gateway and Domain Details: The domain and subnet mask details should already be supplied by the Exadata Provisioning Wizard. Enter a valid IP address for the Admin and Client gateway.
  
  If a private network is used, then select the Custom button and specify the gateway. Typically it is eth0, eth1, or bondeth0.
  
  If the Admin or Client or both networks are configured to use VLAN tagging, then the VLAN IDs are detected and displayed.
- Virtual Machine 1: For the first virtual machine in the cluster, the Exadata Provisioning Wizard will auto-complete the Prefix and Start ID field. You can enter an optional Suffix. Enter a valid IP address.
- Generated Virtual Machine Name and IP: After you have entered the information for the first VM, click Generate to create the information for the other VMs in the cluster. You can always enter the details manually.
Once you have entered all the necessary information, click Validate IP at the top of the page to verify the IP addresses. Click Next to continue to the enter the details for Grid Infrastructure and to create the Initial Database.
On the Grid Infrastructure and Initial Database page, enter the details for:
- Grid Infrastructure: Enter the details for the Cluster (SCAN name and port) and verify the Disk Group information. The Exadata Provisioning Wizard will pre-populate the details, but you can adjust them as needed.
- Initial Database: Click the check box to Create Initial Database. Additional information for Database Identification and Administrator Credentials will be required.
  
  Click Advanced to expand the region for additional details for Memory Parameters, Processes, and Character Sets:
Click Next to set the schedule.
On the Schedule page, the Exadata Provisioning Wizard will create the Deployment Instance value. Select a schedule start and notification options:
- Schedule: Select to initiate the creation immediately or later. If you select later, then you will be prompted to select a date and time.
- Notification: Select the notification statuses for which you will be notified.
Click Review to review the settings and initiate the job.
On the Review page, review the selection in the summary displayed. To change any section, return to the previous page and edit the selection.

Click Submit to begin the creation job.

Scaling Up a Database Cluster

You can scale up the compute ability of your database cluster by creating and adding more virtual machines to the cluster.

From the Database Machine target menu, select Provisioning, then select Scale Up Cluster.

The Exadata Provisioning Wizard will display.
On the Cluster page, enter the cluster name or click the Search icon to select a cluster from the list.

Select one or more from the Available Servers pane, then click the move button to move the selected server to the Selected Servers pane.

Click Next to set the credentials.
On the Credentials page, set the credentials for:
- Compute Server: Set the credentials for the root user. From the Set Credentials drop-down, select All to apply the settings to all servers, or select one or more servers from the list and select Selected to apply the settings to only the selected servers.
  
  In the Set Server Credential pop-up window, select an existing named credential or select New to create a new one.
  
  Click Test Connection to verify that the credentials are properly set. If successful, the Test Credential Status will update to show Succeeded.
- Virtual Machines: Set the credentials for the DomU Host, DomU Root,Cluster ASM, and Cluster Database.
  
  You have the option to use preferred credentials or to override the preferred credentials.
  
  Click Test Connection to verify that the credentials are properly set.
Click Next.
On the Virtual Machines page, click Next.
On the Network page, specify the IP address, name and domain used for the Admin, Client and Private network. Provide the details for the following information:
- Gateway and Domain Details: The domain and subnet mask details should already be supplied by the Exadata Provisioning Wizard. Enter a valid IP address for the Admin and Client gateway.
  
  If a private network is used, then select the Custom button and specify the gateway. Typically it is eth0, eth1, or bondeth0.
  
  If the Admin or Client or both networks are configured to use VLAN tagging, then the VLAN IDs are detected and displayed.
- Virtual Machine 1: For the first virtual machine in the cluster, the Exadata Provisioning Wizard will auto-complete the Prefix and Start ID field. You can enter an optional Suffix. Enter a valid IP address.
- Generated Virtual Machine Name and IP: After you have entered the information for the first VM, click Generate to create the information for the other VMs in the cluster. You can always enter the details manually.
Once you have entered all the necessary information, click Validate IP at the top of the page to verify the IP addresses.

Click Next to continue to schedule the scale up.

Note:

The step for Grid Infrastructure and Initial Database are skipped because they do not need to be set up again.
On the Schedule page, the Exadata Provisioning Wizard will create the Deployment Instance value. Select a schedule start and notification options:
- Schedule: Select to initiate the scale up immediately or later. If you select later, then you will be prompted to select a date and time.
- Notification: Select the notification statuses for which you will be notified.
Click Review to review the settings and initiate the scale up.
On the Review page, review the selection in the summary displayed. To change any section, return to the previous page and edit the selection.

Click Submit to begin the scale up.

Scaling Down a Database Cluster

To scale down a database cluster, the Virtual Machine is removed from the cluster:

From the Database Machine target menu, select Provisioning, then select Scale Down Cluster.

The Exadata Provisioning Wizard will display.
Enter the cluster name you want to scale down or click the Search icon to select an available cluster.
Once you have selected a cluster, you will be prompted to:
- Select nodes to delete.
- Verify or enter new named credentials for DomU (host, root, and Exadata Server) and for the Exadata Storage Server. Click Test Credentials to verify the credentials have been selected properly.
Click Next to schedule the scale-down job.
On the Schedule page, the Exadata Provisioning Wizard will create the Deployment Instance value. Select a schedule start and notification options:
- Schedule: Select to initiate the scale down immediately or later. If you select later, then you will be prompted to select a date and time.
- Notification: Select the notification statuses for which you will be notified.
Click Review to review the settings and initiate the scale down.
On the Review page, review the selection in the summary displayed. To change any section, return to the previous page and edit the selection.

Click Submit to begin the scale down.

Deleting a Database Cluster

You can delete an existing database cluster and free the compute and storage resources used by the cluster. In the provisioning wizard, select the cluster to delete and provide the credentials to access the Exadata Storage Server and the virtual machine hosts.

From the Database Machine target menu, select Provisioning, then select Delete Cluster.

The Exadata Provisioning Wizard will display.
On the Cluster page, enter the cluster name you want to delete or click the Search icon to select an available cluster.

The page will update to show the nodes to be deleted

Verify or enter new named credentials for DomU (host, root, and Exadata Server) and for the Exadata Storage Server. Click Test Credentials to verify the credentials have been selected properly.

Click Next to schedule the delete job.
On the Schedule page, the Exadata Provisioning Wizard will create the Deployment Instance value. Select a schedule start and notification options:
- Schedule: Select to initiate the scale down immediately or later. If you select later, then you will be prompted to select a date and time.
- Notification: Select the notification statuses for which you will be notified.
Click Review to review the settings and initiate the delete job.
On the Review page, review the selection in the summary displayed. To change any section, return to the previous page and edit the selection.

Click Submit to begin the delete job.

Exadata Storage Server Metrics and Alert Settings

To access the settings for Exadata Storage Server metrics/alert:

From the Enterprise Manager home page, select All Targets. Select an Exadata Storage Server.
To change a setting, click Monitoring, then Metric and Collection Settings from the Exadata Storage Server menu. The default View option "Metrics with thresholds" is displayed. You can modify the following parameters:
- Warning Threshold
- Collection Schedule - click the link to set a collection schedule.
- Click the Edit icon for advanced settings.
Click OK to save any changes.

Exadata Storage Server Management

This section provides introductory instructions for managing Exadata Storage Servers. The following topics are presented:

About Exadata Storage Server

An Exadata Storage Server is a highly optimized storage server that runs Oracle Exadata System Software to store and access Oracle Database data. Use the Exadata Storage Server Home page to manage and monitor the Oracle Exadata Storage Server as an Enterprise Manager Cloud Control target. You can discover and consolidate management, monitoring and administration of a single or a group of Oracle Exadata Storage Servers in a datacenter using Enterprise Manager.

Note:

As the Exadata Database Machine has evolved, there have been different names used to reference the Exadata Storage Server, including storage cell and cell server. Any reference with these names in this or related documentation refers to Exadata Storage Server.

Exadata Storage Servers can be discovered automatically or manually. The individual Exadata Storage Server is monitored and managed as an Enterprise Manager target and provides the exception, configuration and performance information.

Grouping of Exadata Storage Servers is used for easy management and monitoring a set of Storage Servers. You can group them both manually and automatically. The grouping function provides an aggregation of exceptions, configuration and performance information of the group of Exadata Storage Servers.

You can view performance analysis by linking Exadata performance both at the Exadata Storage Server level and group level to ASM and database performance. You can drill down to Exadata configuration and performance issues from both the database and ASM targets.

Storage Grid (for example, multiple database/ASM instances sharing the same Exadata Storage Server) is supported to the same extent as dedicated storage.

Viewing an Exadata Storage Server Topology

You can view the topology of an Oracle Exadata Storage Server target by following the steps below:

Navigate to the Exadata Storage Server home page by choosing the Exadata target for which you want to view the configuration.

Enterprise Manager displays the Exadata Storage Server Home page for the target you selected.
From the Target menu, choose Configuration and then Topology.
Enterprise Manager displays the Configuration Topology page for the selected Exadata Storage Server. The topology page provides a visual layout of the target's relationships with other targets. From this page you can:
- Do a target search filtered by target status/events/target type
- Select from a set of relationships to represent in the graph
- Select annotations to display in the graph, such as alerts and link labels
- Select from a set of options: view navigator, expand or collapse all, toggle graph layout, reload topology
- Print
- Zoom via the slide control
- Pan via the navigator control
- Toggle the presentation from graph to table
When you hover over a node or group member, a popup displays detailed information about the entity. A link can appear in the popup to more detailed information such as customer documentation.

Performing Administration Tasks on Exadata Storage Servers

Note:

It is best practice to manage and configure Exadata Storage Servers consistently. Enterprise Manager provides the ability to perform Administration Tasks on all Exadata Storage Servers in an Exadata Database Machine from the corresponding Exadata Storage Server Grid target home page, or on individual Exadata Storage Server targets from the Exadata Storage Server target home page. To the maximum extent possible, consider managing from the Exadata Storage Server Grid target to manage the servers consistently, selecting a subset of servers if necessary. The instructions in this section can be used for either the Exadata Storage Server Grid or Exadata Storage Server targets.

To perform an administration operation on an Exadata Storage Server, such as executing a Exadata Storage Server command, follow these steps:

Navigate to the Exadata Storage Server home page by choosing the Exadata target for which you want to perform an administrative task from the All Targets page.

Enterprise Manager displays the Exadata Storage Server Home page for the target you selected.
Click Exadata Storage Server, and then select Administration.

From this menu you can choose either Execute Cell Command, or Manage I/O Resource.
Click Execute Cell Command.

The Command page of the Exadata Storage Servers Administration wizard appears. Enter a CELLCLI command as the administrative command to be executed on the Exadata Storage Server. You must read the Command Instructions before you enter a command. Only a single cellCLI command is allowed to execute. You must enter the command without the cellcli -e prefix, which is automatically appended when you submit the command. Finally, you cannot use the following characters: ; / ' < > / |.
Click Next to continue.

Enterprise Manager displays the Admin Credentials page. Select or enter the Administration credentials to execute the command. The credentials you enter are used when submitting the operation. You can choose between Preferred Credentials, Named Credentials, and New Credentials. You can also click More Details to view information about Credential Type, Last modified, Credential Name, Credential Owner, Last Modified Date, Last Modified By, and Preferred Credentials Set At.
Click Next.

Enterprise Manager displays the Schedule page. Use the Schedule page to schedule the administration task. Enter the Job Name and the Job Description, then provide the job information in the Schedule the Administration Job section. You can choose to begin the job immediately or enter the time you want the job to begin.
Click Next to continue.

The Summary page displays. Use the Summary page to ensure you have entered the correct values and then submit the command. The Summary page lists the Job Name, Description, Command to Execute, when the job is Scheduled, and the Selected Cell.
Click Submit Command to submit the job.

The Job Status page displays. Use the Job Status page to link to the Job Detail page of the administration task.

Managing the I/O Resource

Oracle Exadata Storage Servers are added as targets during the Exadata Database Machine discovery workflow (see Exadata Database Machine Discovery) and are grouped automatically under the group Exadata Storage Server Grid. Monitoring and Managing I/O Resource can be performed at Exadata Storage Server Grid and Exadata Storage Server target level. The information provided below is for Grid and Server target.

To access the IORM Performance page:

Select an Exadata Storage Server:
1. From the Targets menu, select Exadata.
2. Select a DB Machine from the list of Target Names.
3. In the Target Navigation pane, expand the Exadata Grid item and click one of the Exadata Storage Servers.
Once you have selected an Exadata Storage Server, click the Exadata Storage Server menu, select Administration, then Manage I/O Resource.

The IORM page has the following sections:

I/O Resource Manager Settings: This section helps to view and update the IORM configuration of Exadata Storage Server. Use Get Latest button to view the latest Exadata Storage Server IORM configuration. Use the same section to edit and update the IORM configuration on Exadata Storage Server.
Database Resource Management(DBRM) Settings: This section display the list of databases and their basic configuration, that are using Exadata Storage Server resources. From this page, you can launch the database resource management page.
Workload Distribution by Databases: The IORM Monitoring section of the page provides a view of the performance statistics of Disk I/O (Wait, IOPS, MBPS, Utilization, Latency, and Objective charts). These statistics help to identify which databases and consumer groups are using the available resources. They also help to adjust the IORM configuration (using IORM Settings section on the same page) as needed.

IORM Configuration includes IORM Objective and Inter-Database Plan.

For further details on managing I/O resources, refer to the Managing I/O Resources chapter in the Oracle® Exadata Storage Server Software User's Guide.

Add/Update IORM Configuration

To update the I/O Resource Manager (IORM) settings (for Exadata Storage Server software release 12.1.2.1.0 and later):

Navigate to the IORM page as described above. The image shows the I/O Resource Manager (IORM) Settings pane.

Note:

You can also update a single Exadata Storage Server. Expand the Exadata Grid group to view all Exadata Storage Servers associated with the group. Click the Exadata Storage Server you want to update.

The steps to update the IORM settings is the same for a single Exadata Storage Server or group of Exadata Storage Servers.
Update the inter-database plan by editing existing values or add/remove directives to Inter-database plan using the Add/Remove buttons available on Inter-database table.
1. From the Database Name column, select a database from the drop-down menu or enter a database name.
2. Enter a value for the Hard Disk I/O Utilization Limit column.
3. Enter a value for the Database I/O Share column.
4. Enter minimum and maximum values (in MB) for the Flash Cache column.
5. Fill the remaining attributes like Type and Role.
In the Disk I/O Objective drop-down menu, select an objective from the list (Auto is the default):
- Low Latency - Use this setting for critical OLTP workloads that require extremely good disk latency. This setting provides the lowest possible latency by significantly limiting disk utilization.
- Balanced - Use this setting for critical OLTP and DSS workloads. This setting balances low disk latency and high throughput. This setting limits disk utilization of large I/Os to a lesser extent than Low Latency to achieve a balance between good latency and good throughput.
- High Throughput - Use this setting for critical DSS workloads that require high throughput.
- Auto - Use this setting to have IORM determine the optimization objective. IORM continuously and dynamically determines the optimization objective, based on the workloads observed, and resource plans enabled.
- Basic - Use this setting to disable I/O prioritization and limit the maximum small I/O latency.
Note:
If the Auto and Balanced objectives are not applicable (i.e., they have no impact on I/Os in Extreme Flash Exadata Storage Servers), they will not appear in the IORM page.

Click Update. The Exadata Storage Server Administration Wizard will appear prompting you for the information necessary to complete the Disk I/O Objective configuration:
1. On the wizard's Command page, the Cell Control Command-Line Interface (CellCLI) value should be as shown when the Disk I/O Objective selected is auto:
```
# alter iormplan objective = 'auto'
```
  Click Next.
2. On the wizard's Admin Credentials page, enter the user name and password for the selected Exadata Storage Servers.
  
  Click Next.
3. On the wizard's Schedule page, enter a job name (required) and job description (optional). Select an option to start Immediately or Later. If you select the Later option, enter the time that you want the job to run.
  
  Click Next.
4. On the wizard's Review page, verify that the settings are correct. To submit the command, click Submit Command.
  
  After the job is successfully submitted, the Job Status page is displayed.
  
  Click Return to return to the I/O Resource Manager (IORM) Settings pane.
Click Get Latest to refresh the IORM configuration from Exadata Storage Server, which will include the updated Disk I/O Objective.
To confirm the Disk I/O Objective setting, for example if it was selected as auto, run the following command from the command line:
```
# dcli -g cell_group cellcli -e "list iormplan attributes objective"
```
Output should show the value auto:
```
cell01: auto
cell02: auto
cell03: auto
.
.
.
cell14: auto
```

The Inter-Database Plan

An inter-database plan specifies how resources are allocated by percentage or share among multiple databases for each Exadata Storage Server. The directives (rows) in an inter-database plan specify allocations to databases, rather than consumer groups. The inter-database plan is configured and enabled with the CellCLI utility at each Exadata Storage Server. Only one inter-database plan can be active on a Exadata Storage Server at any given time.

Percentage based Inter-database plan: Use allocations to specify percentage for I/O distribution for each database. With Percentage based plan, IORM can manage up to 32 databases. You can allocate resources across 8 different levels. A percentage based inter-database plan is similar to a database resource plan, in that each directive consists of an allocation amount and a level from 1 to 8. For a given percentage based plan, the total allocations at any level must be less than or equal to 100 percent. An inter-database plan differs from a database resource plan in that it cannot contain sub-plans and only contains I/O resource directives.

Share based inter-database plan: This is the recommended method for Inter-database plans. Use share to specify the relative priority for a database. A higher share value implies higher priority and more guaranteed I/O resources. Each database is given a share value which is an integer between 1 and 32. Use the limit method to restrict the I/O utilization for a database to a specified utilization limit. The sum of the shares can be greater than 100. Share-based plans support up to 1024 directives within the Inter-database plan.

I/O Resource Management can provide predictable performance by guaranteeing space in Exadata Smart Flash Cache. For this use Flash Cache Space columns to specify space allocation for each database in Inter-database plan.

Specify the attributes values for each directive in Inter-database plan as per requirement.

Note:

If the Exadata Storage Server version is 11.2.3.1.0 or earlier, the Share, Percentage based inter-database plan radio buttons are not available. You can view only Percentage-based options (that is, the drop-down only displays the Basic, Advance options).

When considering an inter-database plan:

If Oracle Exadata Storage Server is hosting only one database, then an inter-database plan is not needed.
If an inter-database plan is not specified, then all the databases receive an equal allocation.

Diagnosing Exadata Storage Server Alerts

Enterprise Manager listens for Exadata Storage Server alerts sent from the Exadata Storage Server Management Server; so, any hardware failure or Exadata Storage Server error will be reported in Enterprise Manager. For information about the error messages you might encounter on the Exadata Database Machine, refer to the Error and Alert Messages in Oracle Exadata Database Machine Error Message Reference Guide.

Managing the InfiniBand Fabric

All InfiniBand Switches are discovered automatically during the database machine discovery workflow (see Exadata Database Machine Discovery) and are grouped automatically under the group IBFabric@<switch-name>.

Note:

InfiniBand Fabric target is not available for RoCE Exadata.

From the Enterprise Manager home page, select Targets, then Oracle Exadata Database Machines and Cloud Services.
In the Target Navigation pane, select InfiniBand Fabric from the list.
In the IB Fabric pane, you can view an overview and activity summary for all InfiniBand Switches.
Click Refresh for an On Demand refresh of the InfiniBand schematic. Updates reflect the real-time data.

The following topics address managing your InfiniBand network:

InfiniBand/RoCE Switch Metrics

The Enterprise Manager Agent runs a remote SSH and remote SNMP GET call to collect metric data for the InfiniBand switch. InfiniBand metrics provides operational details such as:

Status / Availability
Port status
Vital signs: CPU, Memory, Power, Temperature
Network interface various data
Incoming traffic errors, traffic Kb/s and %
Outgoing traffic errors, traffic Kb/s and %
Administration and Operational bandwidth Mb/s

The following metrics are available for your InfiniBand Fabric:

Switch Aggregated Status

The Aggregate Sensor takes input from multiple sensors and aggregates the data to identify problems with the switch that require attention. Whenever the sensor trips into an "Asserted" state (indicating a problem) or "Deasserted" (indicating that the problem is cleared) for a component on the switch, associated Enterprise Manager events will be generated.

Response

This is the main metric indicating availability of the InfiniBand/RoCE switch. It is collected every 60 seconds by default through the management interface of the switch.

Switch Configuration

This metric captures the switch configuration. The information collected is valuable only to Oracle Support, which will use it to assist in debugging situations.

Switch Basic Status

This metric gives basic status of the switch like Booted on, Locator light status, Power status and overall status of the switch.

Sensor Status

This metric gives the status of various sensors available in the switch like power supply, fan, motherboard, and cooling.

Switch Port Statistics

This metric provides information on number the of incoming and outgoing errors, incoming and outgoing octets.

Component State

This metric gives the state of various components in the switch like Fan, Motherboard, Power Supply and various InfiniBand and Ethernet ports.

Network Port InfiniBand performance

This metric gives performance data of each InfiniBand port.

Performing Administration Tasks on InfiniBand Networks

Note:

Administrative tasks are not allowed to be performed on RoCE switch.

To perform an administration operation on an InfiniBand Network, follow these steps:

Navigate to the Database Machine home page of the InfiniBand Network by choosing the Database Machine for which you want to perform an administrative task from the All Targets page.

Enterprise Manager displays the Database Machine Home page for the target you selected.
Navigate to System Infrastructure Switch home page for which you want to perform an administrative task.
Go to Administration, and select Switch Operations.
Select the administrative operation you want to execute (Enable/Disable port, Clear performance/Error counters, Switch LED on/off, Set up SNMP subscription). The available operations from which you can select are dependent on the target type and target you selected. Once you choose the operation, you may need to select a value that will appear after choosing the operation.
Click Next to continue.

Enterprise Manager displays the Credentials & Schedule page. Select or enter the credentials to execute the command. The credentials you enter are used when submitting the operation. You can choose between Preferred Credentials, Named Credentials, and New Credentials. Schedule the administration task. Provide the job information in the Administration Job Schedule section. You can choose to begin the job immediately or enter the time you want the job to begin.
Click Next to continue.

The Review page appears. Use the Review page to ensure you have entered the correct values and then submit the command. The Review page lists the Job Name, Description, Command to Execute, when the job is Scheduled, the Target Type, and the Selected Target.
Click Submit Command to submit the job.

When you click Submit Command, a popup is shown if the job is successful. You can go to the Job Detail Page or back to the page from where this wizard was launched.

Setting Up Alerts

After configuring the InfiniBand Switch targets to send SNMP alerts, set up alerts in Enterprise Manager Cloud Control.

Log in to Enterprise Manager Cloud Control.
Click Targets, then All Targets. All discovered targets will display.
In the All Targets page, click Systems Infrastructure Switch.
Click the target you are interested in. The target home page appears.
In the drop-down menu for the Systems Infrastructure Switch, select Monitoring and then Metric and Collections Settings.
In the Metric and Collection Settings page, you can modify metric threshold values, edit monitoring settings for specific metrics, change metric collection schedules, and disable collection of a metric.

You can modify the thresholds directly in the table or click the edit icon (pencil icon) to access the Edit Advanced Settings page. For more information on the fields displayed in this page and how the thresholds can be modified, click Help from the top-right corner of this page.

Flash Cache Resource Monitoring

The Oracle Exadata plug-in release 13.1.0.1.0 and later provides flash cache resource monitoring for Oracle Exadata Storage Servers. The following information is displayed in different sections and pages:

I/O Distribution by Databases: This section on the home page gives the latest performance statistics for the Top 5 databases based on their I/O Utilization.

I/O Distribution for All Databases: This page gives the latest performance statistics for all the databases in the order of I/O Utilization. This page provides both Graph View and Table View. To launch this page, from home page, go to the section I/O Distribution by Databases > Click I/O Distribution for All Databases.

Workload distribution by Databases: This tab on IORM page provides historical performance statistics by databases for both Hard Drive and Flash. You can specify Top 5 databases or specific databases to view their graphs.

Flash Cache Space Usage: This tab on IORM page provides historical statistics specific to Flash Cache Space Usage by databases.

To view the graphs, go to Storage Resources.

Exadata Database Machine Fault Monitoring

Oracle Enterprise Manager Cloud Control provides hardware fault monitoring for Oracle Exadata Database Machine. For a detailed list of the available hardware alert messages, see Hardware Alert Messages for Oracle Exadata Database Machine and Oracle Exadata Rack in Exadata Database Machine Error Message Reference Guide.

Monitoring Exadata Database Machine Components

Enterprise Manager collects details for the following components:

Exadata Storage Servers

An Enterprise Manager Agent could collect Exadata Storage Server metrics through cellcli calls via ssh, ExaCLI or RESTful API. SNMP traps are sent to the Enterprise Manager Agent for subscribed alert conditions.

Monitoring with cellcli requires SSH equivalence to be set up between the agent user and the Exadata Storage Server monitor user on each Exadata Storage Server.

On the home page, rich storage data is collected, including:

Aggregate storage metrics.
Exadata Storage Server alerts via SNMP (PUSH).
Capacities.
Database-level metrics.

Cisco/RoCE Switch (Systems Infrastructure Switch)

An Enterprise Manager Agent runs a remote SNMP get call to collect metric data for the Cisco/RoCE switch, including details on:

Status / Availability
Port status
Vital signs: CPU, Memory, Power, Temperature
Network interface various data
- Incoming traffic errors, traffic kb/s and %
- Outgoing traffic errors, traffic kb/s and %
- Administration and Operational bandwidth Mb/s

ILOM Targets (Systems Infrastructure Server)

An Enterprise Manager Agent runs remote SSH calls to each SI server target.

The following details are collected:

Response – availability
Sensor alerts
- Temperature
- Voltage
- Fan speeds
- Configuration Data: Firmware version, serial number, and so forth.

Power Distribution Units (PDUs)

An Enterprise Manager Agent runs remote SNMP get calls and receives SNMP traps (PUSH) from each PDU. Collected details include:

Response and ping status.
Phase values.

InfiniBand Switch (Systems Infrastructure Switch)

An Enterprise Manager Agent runs remote SSH calls to the InfiniBand switch to collect metrics. The InfiniBand Switch sends SNMP traps (PUSH) for all alerts.

Monitoring requires ssh equivalence for the root or ilom-admin user for metric collections such as:

Response
Various sensor status
- Fan
- Voltage
- Temperature
Port performance data
Port administration

Automatic Indexing for Database Nodes

The automatic indexing feature automates the index management tasks in database nodes with Oracle Database 19.3 or later. Automatic indexing automatically creates, rebuilds, and drops indexes in a database based on the changes in application workload, thus improving database performance.

This feature includes the following options:

Settings: On the Automatic Indexing Configuration Settings page, you can enable and disable automatic indexing, specify the retention period for unused indexes and automatic indexing logs, and specify the schemas to be included or excluded from using automatic indexing.
Activity Report: On the Automatic Indexing Activity Report page, you can enter the following details and click Generate Report to view the details of the auto indexes generated in the database:
- Report Format: Select the format in which you want the report to be generated.
- Sections: Select the sections that you want displayed in the report. The Summary, Index Details, Verification Details, and Errors options are selected by default in the Sections field, and you can opt to remove any of these sections.
- Time Period: Select the monitoring time period for which you want the report to be generated.
If you select the default options, namely the HTML report format and all the options in the Sections field for a specific time period, then the following sections are displayed in the Report Summary:
- Overview of Executions: This section displays the overall performance improvement factor as a result of the auto indexes, the number of times the auto index operations were completed, the number of times the auto index operations were interrupted, and fatal errors, if any. Note that the Overview of Executions section is displayed irrespective of which other section is selected in the Sections field.
- For the Summary section option, the following bar graphs are displayed:
  - Summary of Auto Indexes Actions
  - Summary of Auto Indexes SQL Actions
  - Summary of Manual Indexes
- For the Errors section option, the Error Summary pie chart is displayed.
- For the Index Details section option, the following sections are displayed:
  - Index: Created
  - Index: Dropped
  You can click a row in the Index: Created and Index: Dropped sections to view more details such as the ID of the index that was created or dropped, the Key, and Type. You can also use the Download All Index Created Details and Download All Index Dropped Details options given in these sections to download the index details in a .csv format.
- For the Verification Details section option, the Verification Details section is displayed, which includes the details of the SQLs for which auto indexes were generated and used. You can click a row in this section to view more details such as SQL ID, SQL Text, and Improvement Factor.
If you select the TEXT report format in the Report Format field, then the same information is displayed in a plain text format and can be downloaded by clicking theText Download option.

For information on managing auto indexes, see Managing Auto Indexes in Oracle Database Administrator’s Guide.

Reporting

To monitor the performance of the database machine or the storage server by viewing the metrics and diagnostic data, access the support workbench or create a dashboard for access the database machine reports and capacity planning reports.

Topics:

Accessing Oracle Support Workbench for Exadata Storage Server

You can access the Oracle Support Workbench for the current Exadata Storage Server to access diagnostic data for problems and incidents related to the Exadata Storage Server.

To access the Support Workbench for a single Exadata Storage Server, follow these steps:

From the Target menu of the Exadata Storage Server for which you want to access the Oracle Support Workbench, select Diagnostics, then select Support Workbench.
If you are logging in to the Support Workbench for the first time, you must first initialize the Support Workbench properties. For first-time log in, the Initialize Support Workbench Properties window will be displayed.

Enter the Automatic Diagnostic Repository (ADR) Base Path:

The ADR Home Path is a target-specific, writable path on the agent where the generated package is to be stored. During initializing, it is not editable as it is generated automatically once the ADR base path is specified.

Click Create.
Once the Support Workbench properties have been initialized, the Support Workbench page displays showing a list of any problems for the Database Machine:

Accessing BI Publisher Enterprise Reports

Access the Oracle Business Intelligence (BI) Publisher reports in Oracle Enterprise Manager Cloud Control to run the Exadata reports Exadata Capacity Planning Details and Exadata vCPU Consumption Report to understand the health and utilization of your Exadata portfolio.

To access the Exadata reports in the BI Publisher application from Enterprise Manager:

From Enterprise menu, click Reports > click BI Publisher Enterprise Reports.

The BI Publisher Enterprise Reports page is displayed.
Expand the Exadata Reports tree.

The links to the following reports are displayed:
- Capacity Planning Details: The capacity planning report for Oracle Exadata Database Machine.
- Exadata Cloud Service Capacity Planning Report: The capacity planning report for Oracle Exadata Cloud. See Exadata Cloud Service Capacity Planning Report in Oracle Enterprise Manager Cloud Control for Oracle Exadata Cloud.
  
  Note that the report for Oracle Exadata Cloud has a subset of applicable sections of the Capacity Planning Details report used for Oracle Exadata Database Machine, specifically: Configuration, Global Summary, Storage Capacity Planning Details, CPU and Memory Capacity Planning Details, and IO Capacity Planning Details.
- Exadata vCPU Consumption Report: Total daily vCPU consumption and daily vCPU consumption by compute node and virtual host for Exadata.
Click the link on the report to view it in BI Publisher application. In the resulting report page, you can optionally obtain the report in PDF, HTML, RTF, Excel or PowerPoint formats.

Exadata Capacity Planning Details

Capacity Planning Details report enables you to analyze and visualize the utilization and health of Exadata resources like storage, CPU, memory, IO and network. It also helps to plan for upcoming resource requirements.

Some of the benefits of monitoring your resources:

Optimum Resource Usage: Helps you to fine tune the size and number of resources to ensure that you are getting optimum output
Cost Efficiency: You pay for the exact amount of resources that you will use
Predictive Capacity Planning: Based on the past performance of your configuration, you can plan your resources for future requirements
Improved IT Management: Helps you to keep a close watch on the performance and health parameters of your resources

Exadata Machine Configuration

This section reports the name of the Exadata Database Machine for which the capacity planning report is generated. It also lists the various hosts and their corresponding host types associated with the configuration. The host type can be Database Node or Storage Cell.

Global Summary

This section summarizes the key metrics of your configuration for the time ranges like Last 24 hours, Last 7 Days, Last 31 Days, and Last 365 Days. The same key metrics are analyzed in greater details in the following sections of the report.

The metrics for Last 24 Hours time range are calculated based on the metric collection frequency.

The metrics for the Last 7 Days time range are calculated based on the hourly aggregated data.

The metrics for the Last 31 Days and Last 365 Days time ranges are calculated based on the daily aggregated data.

This is an example global summary of an Exadata Database Machine:

Global summary in the capacity planning report

Storage Capacity Planning Details

As an administrator, you can use the Storage Capacity Planning Details section to diagnose and resolve issues in your storage systems, thus resulting in better performance of not only the storage systems but also the applications relying on them. This section displays the current and historical storage space usage information for all the disk groups.

The current space usage is reported based on the data that was last collected. The following parameters are tabulated for each disk group:

Redundancy
Used (%)
Total Size (GB) - Raw
Free Space (GB) - Raw
Used Space (GB) - Raw
Total Size (GB) - Usable
Free Space (GB) - Usable
Used Space (GB) - Usable

The historical report is generated based on the data available for the selected time range. The following parameters are tracked and plotted in a line chart along the y-axis against time which is on x-axis:

Historical Space Usage By Disk Group (GB) - Usable
Historical Space Usage By Disk Group (%) - Usable
Historical Total Space Usage (GB) - Raw
Historical Total Space Usage (GB) - Usable
Historical Space Usage by the Top 5 Serviced Databases - As seen daily

CPU and Memory Capacity Planning Details

Your CPU and Memory utilizations should not be at critical limits during normal load hours. You should determine CPU and Memory utilizations based on your application needs, including CPU and Memory cycles for peak usage. If your CPU and Memory utilizations are optimized at 100% during normal load hours, you have no capacity to handle a peak load. A mismatch between the capacity and the demands can result in unsatisfactory utilization of resources.

In the CPU and Memory Capacity Planning Details section, CPU Utilization and Memory Utilization parameters of each database node are measured and plotted in line charts for the time ranges Last 24 Hours, Last 7 Days, Last 31 Days, and Last 365 Days.

Following is an example of the CPU Utilization metric for the 24 hours time range:

Following is an example of the Memory Utilization metric for the 24 hours time range:

IO Capacity Planning Details

The IO Capacity Planning Details section displays the current and historical IO, throughput and disk utilization aggregated across all the storage servers for the selected Exadata Database Machine. It summarizes the amount of data being stored in the disks, the read/write throughput rate, and load handling in response to normal and peak demands. Use this section to optimize your disk resources and to plan for future demands.

The following parameters of Cell Disk and Flash are measured and plotted in line charts for the time ranges Last 24 Hours, Last 7 Days, Last 31 Days, and Last 365 Days:

Average Cell Disk Utilization
Aggregate Cell Disk Read and Write throughput
- Disk Read Throughput
- Disk Read Throughput
Aggregate Cell Disk IOPS
- Read IOPS
- Write IOPS
- Total IOPS
Average Cell Disk Load
Average Cell Disk Response Time
Average Flash Utilization
Aggregate Flash Read and Write throughput
- Flash Read Throughput
- Flash Read Throughput
Aggregate Flash IOPS
- Read IOPS
- Write IOPS
- Total IOPS
Average Flash Load
Average Flash Response Time

Following is an example of the average utilization of Flash over a 24-hour time range:

Average utilization of a Flash over a 24-hour time range

Following is an example of the various IO capacity metrics of a Cell Disk over a 24-hour time range:

Network Capacity Planning

The Network Capacity Planning section displays the Bonded (logical) interfaces and Slave (Physical) interfaces throughput. Network bonding corresponds to a single IP address and is the single logical bonded interface formed by aggregating multiple physical network interfaces. Use this section to determine the amount of network traffic handled at various loads.

The section displays the following Transmit and Receive throughputs in Gb/sec for bonded and slave interfaces measured and plotted in line charts for the time ranges Last 24 Hours, Last 7 Days, Last 31 Days, and Last 365 Days:

Transmit - Bonded Interfaces
Receive - Bonded Interfaces
Transmit - Slave Interfaces
Receive - Slave Interfaces

This section does not show the RDS protocol traffic metrics.

Exadata vCPU Consumption Report

Use the Exadata vCPU Consumption Report to track the vCPU usage of your virtualized Exadata Database Machine. Compare the vCPU consumption for different payloads and plan the vCPU allocations for future requirements.

The two parameters used in the report are Exadata target name and time period. The report is generated based on an Exadata target, and defined for the time ranges like 7 Days, 30 Days, 90 Days, 180 Days, and 1 Year, 2 years, 3 years, and 4 years. The default time range is 30 Days. If there is no data on a specific day, then the default value is 0.

Report Summary: The summary includes the selected Exadata target name, selected time period, current total vCPU consumption, and total number of physical CPUs enabled. The last two values add all the current values together from each virtual machine.

The following metrics are generated in the report for the specific Database Machine:

Total Daily vCPU Consumption

Total vCPU consumption is reported based on the time period that you select. For example, if you select 30 days, the data for 30 days including the current date is reported. The details like Exadata target, compute nodes, and hosts are obtained from the Exadata target name and target association relationship. The CPU count is obtained from the historical host configuration metrics. Within a day, only the high value of the number of vCPUs is used for the daily CPU count. On the whole, the CPU count is aggregated by the virtual host for each day. The chart that displays the total vCPU consumption for the time period of 90 days is shown below:

Following is the total vCPU consumption table for a time period of 7 days:

Daily vCPU Consumption by Compute Node and Virtual Host

This table is similar to the table for total vCPU consumption, but without the aggregation of the count. The section presents the data grouped by compute nodes and host.

Following is the daily vCPU consumption of the listed compute nodes and their hosts:

Oracle Exadata Database Machine Dashboard Creation

You can create a Database Machine dashboard to monitor the performance and usage metrics of the Database Machine system, its sub-components, as well as all the database system components residing on the Database Machine.

Exadata Database Machine Dashboard Creation

Log in to Enterprise Manager.
From the Enterprise Manager home page, click the Enterprise menu. Select the Job submenu, then Library.
Select Database Machine Services Dashboard from the drop-down menu next to the Create Library Job option.
Click Go.
Enter a name of the job (for example, CREATE_DBM_DASHBOARD_1).
Click Add and select the DBMachine target. After adding, make sure the target is selected by clicking on the check box next to it. Note that you can select more than one DBMachine and that a dashboard report will be created for each one.
Click the Parameters tab.
Three options are provided through the drop-down:
- Select Create if it is a new report.
- Select Update for updating an existing report with new components.
- Select Cleanup to remove services created by the Create job executed earlier.
Finally, click Save to Library to save the job.

A message indicating the job was created successfully should display along with a link to the running job.

You can monitor the job by clicking on the link corresponding to the job.
To run the job, from the Job Library page, select the newly created job and click Submit. This will open the job to allow you to select the Targets to run against. Select the correct targets and click Submit.

Find All Database Machine Reports

To find all Database Machine reports:

Log in to Enterprise Manager.
From the Enterprise Manager home page, click the Enterprise menu. Select Reports, then Information Publisher Reports.
Search for the report name. Dashboard report names, one for each Database Machine, are displayed in the following format:
```
[DBMachine Name]_DASHBOARD_REPORT
```
Click on the report to view the dashboard report.

How to Make the Report "Public"

The generated report is accessible only by the Enterprise Manager user who creates it. To make the report public:

Select the dashboard report from the list of Information Publisher reports shown after following the steps mentioned above.
Click Edit.
Select the Run report using target privileges of the report owner option under Privileges section in General tab.
Click the Access tab.
Select the Allow viewing without logging in to Enterprise Manager option.
Click OK.