1z0-902 Exam Dumps - Oracle Exadata Questions and Answers

To enable REST access to the MS process, you need to manually enable the REST services on each storage server by running the command cellcli -e "ALTER CELL ENABLE REST" and then configure authentication and authorization to ensure secure access. This is described in detail in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (Chapter 8, Securing the Exadata Database Machine).

https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/access-rest-api.html

On Oracle Exadata Database Machine X9M, the default configuration of the IPTables firewall varies between storage servers and database servers:

Storage Servers: After initial deployment, IPTables is installed but remains in an unconfigured and inactive state. The Exadata storage servers focus on providing high availability and performance for database workloads and thus rely on internal security measures. The external firewall or network security policies typically handle firewall responsibilities, so IPTables is not actively configured on these servers by default​​.

Database Servers: Similar to storage servers, IPTables is also installed but neither configured nor running on the database servers. The Oracle Exadata Database Machine X9M emphasizes security through other means, such as its network isolation and dedicated interconnects. As part of Oracle’s engineered systems design philosophy, the database servers are primarily focused on database performance, offloading much of the security management to other parts of the infrastructure and relying on data center-level firewalls for perimeter security​​.

To summarize, both database and storage servers have IPTables installed and available, but they are not configured or running by default on either server type. This setup allows Exadata environments to focus on optimized database performance while integrating with external network security solutions.

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/maintaining-exadata-storage-servers.html#GUID-AE16A1DA-53C6-4E80-94E5-963AA65373AB

The two commands that must be executed to safely power off the storage server in an Exadata X9M Database Machine are E and F.

Command E, CellCLI alter GRIDDISK all inactive, will deactivate all of the GRIDDISKS on the affected storage server. This will ensure that no data is lost during the power-off process.

Command F, shutdown -h now, will shut down the storage server. This will ensure that the storage server is completely powered off and no data is lost.

For more information on how to properly power off an Exadata Storage Server, refer to the Oracle Exadata Database Machine X9M Implementation Essentials official text book and resources [1][2].

https://support.oracle.com/knowledge/Oracle%20Database%20Products/1188080_1.html

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

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.

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

For adding a new RAC (Real Application Clusters) VM cluster to an existing Oracle Exadata X9M-2 deployment, you can utilize the Oracle Exadata Deployment Assistant (OEDA). OEDA is available in two interfaces:

OEDA Web-based Configuration Tool: This web-based interface facilitates the configuration of Exadata environments, supporting both physical and virtual deployments. The graphical interface helps in defining VM clusters, including RAC clusters, and ensures the configuration aligns with Oracle best practices​.

OEDA Command Line Interface (CLI): For more advanced or automated tasks, the command-line interface (oedacli) allows for precise control over the deployment process. It supports various configuration actions such as adding or removing clusters, resizing ASM disk groups, and managing VM clusters​.

These tools are specifically designed for Exadata configurations and provide a streamlined approach for deploying and managing RAC clusters in both physical and virtualized environments.