Oracle 1z0-902 - Oracle Exadata Database Machine X9M Implementation Essentials

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

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

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

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

C. OEDA deployment steps include calibrate cells, create cell disks, and resecure machine2.

D. OEDA sets up key-based authentication for the root user by using the setuprootssh.sh utility included with OEDA2.

Option 5 stops the clusterware on all database servers as the grid user3.

Option 8 shuts down all Exadata storage servers using their ILOM interfaces1.

Option 7 shuts down all database servers using their ILOM interfaces1.

Option 6 powers off the rack using the power switches on the PDUs2.

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

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

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

The correct sequence is:

Review the safety guidelines. This is important to ensure a safe and successful installation1.

Unpack Oracle Exadata Rack. This involves removing the packaging materials and inspecting the rack for damage or missing components1.

Place Exadata in its allocated space. This involves moving the rack to its final location and securing it with bolts and brackets1.

Let the Exadata acclimatize for 24 hours. This is recommended to allow the rack components to adjust to the ambient temperature and humidity before powering on1.

Stabilize the Exadata Rack. This involves leveling the rack and adjusting its height if needed1.

Power on Exadata PDU B. This involves connecting PDU B to a power source and turning it on1.

Power on Exadata PDU A. This involves connecting PDU A to a power source and turning it on1

The given command uses a for loop with ipmitool to issue ping commands sequentially to a range of IP addresses in the management network:

for j in {01..23}; do ipmitool sunoem cli "set /SP/network/test ping=192.168.1.1$j"; done

This script verifies the connectivity of the ILOM management network before the Exadata installation. Each server’s Service Processor (SP) is tested for reachability, confirming that the management network setup is operational across the full rack .

This SQL statement is adding the new griddisks to the existing diskgroup "DATA" and creating one new failgroup, consisting of all 96 griddisks. The "REBALANCE POWER 512" option tells the system to perform a rebalance operation with a power of 512. It means the system distributes the data evenly across all the disks in the diskgroup using a power of 512.

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.