Download Full Version 1z0-902 Oracle Exam

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​​.

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.

Oracle KVM Guest: This is a virtual machine that runs on top of Oracle Linux KVM hypervisor. It can be used to run Oracle Database or other applications on Exadata Database Machine2. Therefore, it runs on the Database Servers.

Oracle Enterprise Manager Agent (OMA): This is a software agent that communicates with Oracle Enterprise Manager Cloud Control and provides monitoring and management capabilities for Exadata Database Machine2. Therefore, it runs on both Database Servers and Storage Servers.

ASM instance: This is an instance of Oracle Automatic Storage Management (ASM), which is a volume manager and a file system for Oracle Database files. It manages disk groups that span across multiple Storage Servers2. Therefore, it runs on the Database Servers.

RDBMS instance: This is an instance of Oracle Database that processes SQL statements and executes transactions. It uses ASM disk groups to store data files, control files, redo log files, etc2. Therefore, it runs on the Database Servers.

Automatic Diagnostic Repository Command Interpreter (ADRCI): This is a command-line tool that enables you to view diagnostic data stored in the Automatic Diagnostic Repository (ADR). ADR is a file-based repository for database diagnostic data such as trace files, alert logs, etc2. Therefore, ADRCI runs on both Database Servers and Storage Servers, depending on where the ADR is located.

CELLCLI: This is a command-line interface that enables you to configure and manage Exadata Storage Server Software. It allows you to perform tasks such as creating disk groups, monitoring cell health, applying patches, etc2. Therefore, it runs on the Storage Servers.

Cell Server(CELLSRV): This is a process that runs on each Storage Server and handles I/O requests from the Database Servers. It implements Exadata Smart Scan , which offloads data-intensive SQL operations from the Database Servers to the Storage Servers2. Therefore, it runs on the Storage Servers.

diskmon: This is a process that monitors the status of disks and flash devices on each Storage Server. It reports disk failures and performs automatic disk reclamation2. Therefore, it runs on the Storage Servers.

Restart Server (RS): This is a process that manages automatic restarts of critical processes such as CELLSRV , MS , or OMA in case of failures. It also handles graceful shutdowns and startups of all processes on each server2. Therefore, it runs on both Database Servers and Storage Servers.

Management Server (MS): This is a process that provides management services for each server such as collecting metrics , logging events , executing commands from CELLCLI , etc2. Therefore, it runs on both Database Servers and Storage Servers

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