1z0-902 Questions and Answers

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

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 the Oracle documentation1, 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.

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.

Oracle ASR covers a range of hardware components on Exadata Database Machines to ensure rapid response and issue resolution. The covered hardware components include critical parts such as:

Fan Trays: These are essential for cooling Exadata components and are covered by ASR in case of failures​.

System Controller (SC): Integral to the operation of Exadata storage servers, SC failures are reported by ASR to ensure the overall system’s reliability and availability​.

I/O Boards: ASR actively monitors and responds to failures in I/O boards, which are crucial for data processing and connectivity within Exadata storage servers​.

The ASR system is optimized to handle hardware-related issues proactively, ensuring that critical components are continuously monitored and replaced as necessary.

According to Oracle’s documentation1, the customer options for hosting the Platinum Services Advanced Support Gateway are:

Provide individual x86 64-Bit gateway hardware1

Purchase the recommended x86 64-Bit gateway hardware from Oracle1

Install on Oracle Database Appliance2

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

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 .

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.

According to the web search results123, the storage servers in an Exadata Database Machine are mainly used for processing data at the storage level and offloading some SQL operations from the database servers. Therefore, the two activities that are supported on the storage servers are:

A. changing the root password

E. configuring secure shell user equivalency for the cellmonitor user

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmso/exadata-introduction.html

According to the Oracle Auto Service Request (ASR) documentation1, ASR raises service requests for qualified Oracle products that are detected with specific faults. The qualified Exadata products include2:

Database servers

Storage servers

InfiniBand switches

Cisco switches (X8M and later systems)

Power distribution units (PDUs)

Once the physical disk has been replaced, you will need to create a new celldisk and griddisks on the replaced physical disk. After the griddisks have been dropped from the associated ASM diskgroups, you can then add the griddisks back into the ASM diskgroup they used to be a member of and rebalance the data on the effected griddisks. Finally, you should verify that the griddisks located on the physical disk have been successfully dropped from the associated ASM diskgroups.

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

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

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

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.

The minimum Exadata System Software version required to support Oracle Exadata X9M is 21.2.0.0.0. This version introduced various enhancements and capabilities tailored for the X9M series, including optimizations for the RoCE network fabric and support for new hardware components .

A and E are the two correct quarantine types that can disable Smart Scan for multiple databases that offload SQL statements to a cell on an Exadata Database Machine. A is correct because SQL Plan Quarantine will disable Smart Scan for all queries related to the SQL plan that was placed in the SQL Plan Quarantine [1]. E is correct because the Cell Offload Quarantine will disable Smart Scan for all queries offloaded to Oracle Database Exadata Storage Server Software [2]. The other statements (B, C, and D) are incorrect.

[1] Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book , Chapter 13 [1][2]: Oracle Database Exadata Storage Server Software [2] Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book , Chapter 15 [1][2]: Oracle Database Exadata Storage Server Configuration

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-storage-server-software-introduction.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.

According to the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and Resources, you can find diagnostic messages related to this problem in the alert logs for the ASM instances and the alert logs for the prod database instances. The alert logs for the ASM instances will provide information related to the offline asm disks, while the alert logs for the prod database instances will provide information related to whether the prod database instances are connected to the ASM instance or not.

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-administering-asm.html