1z0-902 Oracle Exadata Database Machine X9M Implementation Essentials Questions and Answers

The CELLCLI CALIBRATE command can be used to check the health of all flash cards in the storage server, and it should be run after logging in as the celladmin user. The hardware monitoring using the storage server ILOM should also be used to check for errors and other potential issues with the flash cards. The CELLCLI list LUN DETAIL command should not be used to identify a damaged or failing flash card, since it will not provide any information about the health of the flash card.

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

The two valid reasons are:

• corruption in the / (root) filesystem . According to 1, this is one of the scenarios that requires a storage server rescue procedure , because it prevents the storage server from booting up normally . The rescue procedure will re-image the root filesystem with a fresh copy of the operating system and restore the configuration files from a backup1.
• the failure of both physical M.2 disks . According to 2, each Exadata Storage Server X9M-2 has two physical M.2 disks that store the operating system and configuration files for the storage server . If both M.2 disks fail , then the storage server cannot boot up or function properly . The rescue procedure will replace the failed M.2 disks with new ones and re-image them with the operating system and configuration files2.

Your customer needs to ensure that their data is available on the Exadata machine during updates. The customer wants to be able to update one server at a time but still be protected against single-node server failure. This means that they need a redundancy level that can tolerate at least one disk failure without losing data availability or performance. Therefore, the best option for them is normal redundancy . Normal redundancy provides two-way mirroring by default, which means that each data extent has a primary copy and a mirror copy on different disks in different failure groups1. A failure group is a subset of disks within a disk group that are likely to fail at the same time due to common dependencies2. On Exadata Database Machine , each Storage Server is considered as a failure group by default2. This means that if one Storage Server fails or needs to be updated , the data on its disks can still be accessed from another Storage Server that has the mirror copies of the same data extents2. Therefore, normal redundancy ensures data availability and performance during updates or single-node server failures.

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

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

According to the Oracle Exadata Database Machine Technical Architecture1, the initial storage configuration after the standard (non-virtualized) deployment of a new Exadata Database Machine with High Capacity storage servers includes two ASM disk groups: DATA_ and RECO_. These disk groups are built on hard disks and flash disks inside the Exadata Storage Servers1.

The correct statements about this configuration are:

• Option D: There is free space available on flashdisks inside the Exadata storage servers for possible use for storage indexes. Storage indexes are a feature of Exadata Storage Software that can improve query performance by avoiding unnecessary I/O operations. Storage indexes use a small amount of flash memory to store metadata about data blocks stored on disk1.
• Option E: There is free space available on flashdisks inside the Exadata storage servers to configure Exadata Smart Flash Logs. Exadata Smart Flash Logs are another feature of Exadata Storage Software that can improve database performance by using flash memory as an extension of the database redo log buffer. This can reduce latency and increase throughput for redo log writes1.