Exadata storage realms using ASM-scoped security mode allows you to control which database can access which griddisks by creating realms at the ASM level, thereby allowing you to limit the access of each database to the griddisks that it needs to access. This is covered in section 3.15.2 of the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and Resources [1].

Exadata storage realms using database-scoped security mode allows you to control which database can access which griddisks by creating realms at the database level [1], thereby allowing you to limit the access of each database to the griddisks that it needs to access. This is covered in section 3.15.3 of the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and Resources [2].

[1] https://docs.oracle.com/en/engineered-systems/exadata-database-machine/x9m/exad-implementing-database-machine-x9m.pdf  [2] https://docs.oracle.com/en/engineered-systems/exadata-database-machine/x9m/exad-implementing-database-machine-x9m.pdf

In order to monitor all components of this multirack configuration, Enterprise Manager agents must be deployed on at least two storage servers in both racks and all database servers in both racks. This is according to the Oracle Exadata Database Machine X9M Implementation Essentials official text book [1], in which it states "To monitor all components of the multirack configuration, you must deploy agents on all database servers and at least two storage servers in each rack" (page 6-15).

According to the Oracle documentation1, two statements that are true about enabling write-back flash cache are:

Write-back flash cache is on by default for High Capacity Storage Servers in High Redundancy configurations (A). This is because write-back flash cache provides better performance and reliability for data file writes than write-through flash cache.

Before write-back flash cache is enabled, you need to drop the Flash Cache first (D). This is because changing the flash cache mode requires recreating the flash cache with a different configuration.

According to 1, Exadata X9M-2 Database Servers are based on Intel Xeon Platinum 8368Y processors with 32 cores and 768 GB of DRAM memory per server. This memory can be expanded up to 1.5 TB per server by adding 24 x 32 GB DIMMs. The DRAM memory is used for buffer cache, PGA, and other database purposes1. Exadata X9M-2 Database Servers also have 25.6 TB of Persistent Memory Acceleration (PMEM) per server, which is used for log writes and columnar data caching1. PMEM is a new type of memory that combines the speed of DRAM with the persistence of flash2. Exadata X9M-2 Database Servers are designed to run Oracle Database workloads with high performance, scalability, and reliability2

The statements that are true about the CellCLI command are:

It has command-line history . According to 1, you can use the up and down arrow keys to scroll through previous commands that you entered in CellCLI . You can also use Ctrl+R to search for a previous command by entering part of it .

It can be executed on storage servers . According to 1, you can invoke CellCLI by logging in to the Exadata cell as cellmonitor , celladmin , or root user and typing “cellcli” . Within CellCLI , you can perform various management and monitoring tasks for the cell134.

It can be executed using the DCLI utility . According to 5, DCLI (distributed CLI) is another utility that can be used to execute scripts and commands across multiple storage cells from a single interface. You can use DCLI to run CellCLI commands on multiple cells at once54.

According to Oracle’s documentation1, the client network on Exadata X9M-2 Database Server is used for client access to the database servers using Single Client Access Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses. To verify that the client network is available via both client switches, you can use the command:

cat /proc/net/bonding/bondeth0

This command displays information about the bondeth0 interface, which is used for the client network on Exadata X9M-2 Database Server2. You can check if both interfaces (eth0 and eth1) are active and connected to different switches3.

The Exadata X9M-2 Extended (XT) Storage Server does not include any Persistent Memory (PMEM) DIMMs. The XT server configuration primarily serves as a cost-effective archival storage option and lacks the performance features available in the HC (High Capacity) and EF (Extreme Flash) storage servers. This configuration does not include Persistent Memory, which is leveraged in other models for accelerating OLTP workloads and providing extremely low-latency data access​​.

This command will display the name, deviceName, diskType and physicalFirmware attributes of the physicaldisks in a storage server, as explained in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (page 85).

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-storage-server-cellcli.html

In order for an Exadata X9M-2 Elastic Rack to be installed, two power feeds are required for each of the three-phase 24kVA PDUs. A single cable from each PDU will not be enough to power the rack, and neither a splitter cable nor rearrangement of the power cables from the servers to the PDUs will be able to provide sufficient power for the system. Therefore, the installation cannot proceed until two power feeds are available per PDU.

For more information about power requirements for Exadata X9M-2 Elastic Racks, refer to the Oracle Exadata Database Machine X9M Implementation Essentials official text book and resources.

Search results: [1] Oracle Exadata Database Machine X9M-2 Full Rack Installation - Oracle Docs [2] Exadata Database Machine X8M-2 Mid-Size Rack Installation - Oracle Docs

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmin/exadata-site-requirements.html

For setting up Auto Service Request (ASR) monitoring on a standalone server dedicated to ASR Manager:

ASR Manager with SNMP Traps: Configuring ASR Manager to utilize SNMP traps allows it to automatically receive alerts from the Integrated Lights Out Manager (ILOM) on Exadata components. The SNMP traps notify ASR Manager of specific hardware faults or critical system events, which then automatically generate service requests with Oracle Support​.

This setup ensures proactive monitoring and allows rapid response to any critical alerts related to the Exadata hardware, leveraging the ILOM’s ability to monitor key system health metrics and trigger alerts as necessary.

Statement B is true as the vm_maker —start-domain command can be used to start a virtual machine manually, as stated in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (page 65).

Statement E is also true as the vm_maker —auto-start command can be used to configure a virtual machine to start automatically when the KVM host is started [1][2], as stated in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (page 66).

High Capacity (HC) Storage Server: The Exadata X9M-2 HC storage server is configured with a combination of hard disks and flash memory, providing a balance of storage capacity and performance.

It includes 12 x 18 TB hard disk drives, which totals 216 TB of raw disk capacity​.

For flash storage, it has 4 x 6.4 TB PCIe flash cards totaling 25.6 TB of flash storage. This configuration uses NVMe Flash Accelerator F680 cards optimized for database caching​​.

The persistent memory in the HC server totals 1.5 TB, enhancing performance for OLTP (Online Transaction Processing) workloads by providing ultra-fast access speeds compared to traditional flash storage​.

Extreme Flash (EF) Storage Server: The EF storage server in the Exadata X9M-2 model is an all-flash storage server designed for high IOPS and low latency, making it ideal for performance-intensive workloads.

This configuration contains 8 x 6.4 TB PCIe flash cards, providing a raw capacity of 51.2 TB of high-performance flash storage​.

In terms of persistent memory, it includes 756 GB of Intel Optane Persistent Memory. This enhances flash storage performance by offloading data processing directly to persistent memory​​.

The Exadata X9M-2 storage configurations—both HC and EF—are optimized for different workload requirements. The HC configuration caters to larger datasets needing high storage capacity, while the EF configuration is designed for workloads requiring high throughput and minimal latency.

A. YOU query VSSYSTEM_EVENTS and filter for the event ‘cell physical IO interconnect bytes returned by smart scan’, associated to your table. This does not show how much data was filtered by Smart Scan, but only how much data was returned after Smart Scan12.

C. You query v$SYSTAT and filter for the statistic ‘cell smart table scan’, associated to your table. This does not show how much data was filtered by Smart Scan for a specific table, but only for all tables in a session12.

https://www.databasejournal.com/oracle/monitoring-smart-scans-in-oracle-exadata/

The dbmcli -e "LIST IBPORT DETAIL" command is not valid on Exadata X9M. According to the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book [1][2], this command is only valid on Exadata X3 and X4 models. The other three commands are valid on Exadata X9M.

https://forums.oracle.com/ords/apexds/map/tech/apps-infra/discussion/4342715/monitoring-roce-performance

According to Oracle’s documentation1, one of the utilities for diagnostics and repair of Oracle Exadata Storage Server is ExaWatcher, which collects operating system and network metrics on database servers and storage servers. The utility is located in the /opt/oracle.ExaWatcher directory1.

To investigate why an Exadata Database Server stopped communicating on the client network for 10 minutes over the past weekend, you can use the GetExaWatcherResults.sh script to collect and analyze ExaWatcher data for a specified time range1.

Therefore, the command that you should use to investigate this is:

/opt/oracle.ExaWatcher/GetExaWatcherResults.sh —from _17:00:00 —to _23:59:00

In an Exadata environment, the path of communication for SNMP traps involves:

Management Server (MS) Process to EM Agent: Alerts related to the storage server are generated by the MS process, which then forwards SNMP traps directly to the Enterprise Manager agent, allowing centralized monitoring and alert management​.

ILOM to EM Agent: The ILOM on each Exadata storage server can independently send SNMP traps to the EM agent, providing additional hardware-level monitoring and alerting capabilities .

These pathways ensure that alerts from both hardware and software layers reach Enterprise Manager efficiently, supporting proactive management and rapid response to system issues.

For a non-virtual deployment of Oracle Exadata with a single cluster:

Single Client Access Name (SCAN) Listeners: By default, three SCAN listeners are configured on the RDMA over Converged Ethernet (RoCE) network. This setup allows for load balancing and high availability of incoming client connections across the cluster nodes​.

Oracle Cluster Registry (OCR) Multiplexing: The OCR is typically stored in multiple locations within the disk groups to enhance reliability and fault tolerance. On Exadata, the OCR is multiplexed across the DATA and RECO disk groups for enhanced resilience​.

ora.diskmon Resource: This is an essential component of Oracle Clusterware, responsible for monitoring and managing disk-related cluster resources. It is always enabled and kept online by Oracle Clusterware on Exadata systems​.

According to Oracle.com documents or resources, the three options that are available for database consolidation on Exadata are:

A. Multiple pluggable databases in one or more container databases on a Virtual Machine or Bare Metal cluster123.

C. A single database with one or more schema per application12.

E. Multiple Databases on a cluster12.

https://blogs.oracle.com/exadata/post/database-consolidation-why-and-how

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

https://chriscraftoracle.wordpress.com/2022/11/09/what-makes-exadata-faster/

According to Oracle’s documentation12, some of the statements that are true about applying updates on Exadata systems are:

Failed storage server updates are automatically rolled back to a previous release1.

When running a “yum update” for a new Exadata release, all other repositories should be disabled1.

To drop all celldisks on all the storage servers in an X9M-2 quarter rack, you should use the CELLADMIN account, which has the necessary privileges to perform this task. You can use the CELLCLI command-line interface to drop the celldisks. The best way to do this is by calling CELLCLI on all cells using DCLI (Oracle Database Command Line Interface) which allows you to run commands on multiple servers at once. Alternatively, you can use an administrator-created storage server user with appropriate privileges on celldisk objects by calling CELLCLI on all cells using exadcli. It is not recommended to use the CELLMONITOR account, as it has a more limited set of privileges. It is also important to note that EXACLI is not a valid tool for this task

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/maintaining-exadata-storage-servers.html

Exadata System Software metrics and alerts work as follows:

Persistence of Thresholds: When metric thresholds are configured, they remain active and persist across server reboots. This ensures consistent monitoring behavior even after maintenance or unexpected reboots .

Default Metrics: By default, metrics are collected without predefined thresholds. Administrators must set custom thresholds to enable specific alerting based on their operational requirements​.