Option C shows the number of read hits from PMEM cache on storage servers which indicates how much data was served from PMEM instead of flash or disk 1 .

Option E shows detailed information about PMEM cache such as size, utilization, hit ratio, read latency and write latency 2 .

According to the Oracle documentation 1 , two monitoring tools that might be useful in examining I/O performance for the prod database are:

cellcli (or exacli/exadcli)  to examine storage server metrics such as database, category, ceiidisk, and griddisk (D). This tool can help you monitor the I/O Resource Management (IORM) metrics and identify any bottlenecks or imbalances in the storage layer.

I/O-specific dynamic performance views  such as v$iostat_fiie, v$iostat_function, and v$iostat_consumer_group from the prod database instances using SQL *p1us ©. These views can help you monitor the I/O activity and latency at the file, function, and consumer group level.

https://www.oracle.com/a/ocom/docs/engineered-systems/exadata/exadata-x9m-2-ds.pdf

For Exadata systems, hardware monitoring for components like the motherboard, memory, power, fans, and network cards on the database nodes is managed through the Integrated Lights Out Manager (ILOM). The ILOM provides built-in thresholds and sensor readings that are automatically recognized by Oracle Enterprise Manager.

These thresholds and alerts are already configured within ILOM for Exadata components, ensuring seamless integration with Enterprise Manager for alerting and monitoring purposes​.

Enterprise Manager uses these pre-set ILOM thresholds and does not require additional configuration for monitoring hardware components. Therefore, administrators benefit from preset alerting mechanisms that are sufficient for comprehensive hardware status visibility​.

It collects configuration information automatically  (B).  OCM gathers detailed configuration information about a variety of designated Oracle products and components across an enterprise on a regular basis 2 .

It collects configuration information on demand  ©. OCM can also collect configuration information manually when requested by the user or by Oracle Support 2 .

Collected configuration information can be uploaded automatically to Oracle  (E).  OCM can upload the collected configuration information to My Oracle Support automatically for analysis and support purposes 3 .

Oracle Exadata X9M-2 supports virtualization through Kernel-based Virtual Machine (KVM), enabling multiple virtual machines (VMs) to run on each database server. Specifically:

Each X9M-2 database server can support up to 12 virtual guests . This number provides ample flexibility for running various applications or Oracle Real Application Clusters (RAC) instances across virtualized environments .

While Exadata X9M-8 supports even more extensive virtualization, this question focuses on the X9M-2 model. The specified limitation of 12 guests per database server considers both system resource allocation and performance optimization .

According to Oracle.com documents or resources, the four actions that you should take before proceeding with applying updates to your Exadata Database Machine are:

A.  Consult My Oracle Support note 888828.1 to determine the current recommended Exadata software release 1 2 3 .

B.  Check the Exadata Critical Issues My Oracle Support note 1270094.1 for any issues not added to the latest version of exachk 4 5 3 .

C.  Run exachk and resolve only WARNINGS that you have not seen before 3 .

D.  Run the appropriate patchmgr preqequisite check step for each component being updated 3 .

Oracle Auto Service Request (ASR) on Exadata Database Machines is designed to proactively monitor and detect hardware and software issues. When a problem is detected, ASR Manager automatically opens a service request (SR) with Oracle Support. The primary focus of ASR is on hardware assets, such as storage servers, database servers, and network components, as well as software assets related to Exadata System Software and Oracle Database configurations​​.

On Exadata systems, ASM disk group configurations require that:

Grid Disks Must Have Similar Performance Characteristics : Within a disk group, grid disks must not only be of the same size but also need to exhibit similar performance traits. This consistency ensures balanced I/O operations and optimizes the performance for ASM mirroring and striping across disks​.

Sparse Diskgroups : These are specialized virtual objects that reside within the DATA disk group. Sparse diskgroups are used to support snapshots and other space-efficient storage solutions by creating virtual representations of grid disks within an existing disk group without consuming additional physical space​.

These characteristics are fundamental to ensuring that ASM maintains optimal performance and storage efficiency on Exadata platforms.

The Oracle Exadata Deployment Assistant Command Line Interface (OEDACU) supports a variety of configuration and lifecycle management tasks for Exadata systems, such as adding or removing nodes, resizing ASM disk groups, and managing Oracle Database home directories. However, it does not support lifecycle management for the Zero Data Loss Recovery Appliance (ZDLRA), as this device requires different management tools specific to its backup and recovery functions .