Oracle 1z0-902 Oracle Exadata Database Machine X9M Implementation Essentials Exam Practice Test

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.

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

For Exadata systems, hardware monitoring for components like the motherboard, memory, power, fans, and network cards on the database nodes is managed through the Integrated Lights Out Manager (ILOM). The ILOM provides built-in thresholds and sensor readings that are automatically recognized by Oracle Enterprise Manager.

These thresholds and alerts are already configured within ILOM for Exadata components, ensuring seamless integration with Enterprise Manager for alerting and monitoring purposes​.

Enterprise Manager uses these pre-set ILOM thresholds and does not require additional configuration for monitoring hardware components. Therefore, administrators benefit from preset alerting mechanisms that are sufficient for comprehensive hardware status visibility​.

D. ASR can upload configuration metadata to support problem resolution1.

E. ASR Manager opens a service request (SR) automatically after sensors detect hardware faults1

https://docs.oracle.com/cd/E37710_01/doc.41/e23333/toc.htm

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

The correct order of steps is 10, 8, 9, 11. The 10th step is to use the drop down to add Exadata X9M Database Servers, the 8th step is to use the drop down to add Exadata X9M EF Storage Servers, the 9th step is to use "Add Equipment" to add the ZFS Storage Controllers, and the 11th step is to use "Add Equipment" to add the ZFS Storage Trays. These steps are referenced in the Oracle Exadata Database Machine X9M Implementation Essentials Official Textbook, which is available online at https://docs.oracle.com/cd/E80437_01/E80437/html/index.html.

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmin/configuring-exadata.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)

After running the commands above, the filesystem mounted on /u01 is on the logical volume /dev/mapper/VGExaDb-LVDbOral. So, to add 20G of space to the filesystem mounted on /u01, the command that needs to be run is:

lvextend -L +20G --verbose /dev/mapper/VGExaDb-LVDbOral

This command will extend the logical volume /dev/mapper/VGExaDb-LVDbOral by 20 GB of space. It is important to note that the option --verbose is used to display the progress of the operation.

B and E are true statements for the Oracle Exadata Configuration Assistant (OECA). OECA facilitates PDU power selection initially and after equipment addition, and it allows for the elastic configuration of the hardware. It does not reconfigure the size of disk groups or recreate grid disks, nor does it allow for a single XT storage server in the configuration. The "Add Equipment" input option does allow for the allocation of RU slots for customer equipment.

References for this information can be found in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and Resources.

Search results: [1] Oracle Exadata Database Machine X8-2 [1][2]: Configuration Assistant Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can … [2] The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can be used to … Add Equipment: This input option allows you to allocate RU slots for … [3] Oracle Exadata Database Machine X7-2 and X7-2L Installation Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can … [4] The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can be used to … Power Selection [1][2]: This input option allows you to select PDU power initially … [5] Oracle Exadata Database Machine X7-2 and X7-2L Installation Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can …

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.

To monitor the effectiveness of Persistent Memory (PMEM) cache usage with RDMA on Exadata, information on RDMA I/O statistics can be found in:

PMEM Cache User Reads section in the AWR Report: This section provides detailed statistics on PMEM read operations, including user reads that leverage RDMA for direct memory access from PMEM. These metrics help gauge the utilization and efficiency of the PMEM cache​.

Exadata Metrics (LIST METRICCURRENT): By using the LIST METRICCURRENT command within the Exadata environment, real-time metrics related to PMEM usage and RDMA I/O statistics can be accessed. This provides an immediate view of the current performance and activity on Exadata’s persistent memory components​.

These tools together offer insights into PMEM cache usage and the effectiveness of RDMA for optimized data access.

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.

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.

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

Oracle Exadata Deployment Assistant (OEDA) offers multiple benefits for configuring and deploying Exadata systems:

Configuration Gathering and Rack File Creation: OEDA simplifies the setup of Exadata environments by collecting system-specific configuration details. It uses this information to generate the Exadata Rack configuration file, which outlines the optimal setup for the particular environment, streamlining the deployment process and ensuring compatibility with Oracle best practices​ .

Lifecycle Management CLI for Exadata Systems: OEDA includes a command-line interface (CLI) that facilitates various lifecycle management tasks, specifically designed for Exadata systems. This CLI helps in automating deployment steps, adjusting configurations, and updating system parameters, tailored specifically for Exadata’s hardware and software environment .

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 .

Exadata Secure RDMA Fabric isolation is a feature that allows you to use virtualization on the X9M-2 platform while maintaining security and isolation between multiple tenants or VM clusters. Secure Fabric isolation works by creating a dedicated network partition and VLAN ID for each Database VM cluster, which is used for cluster networking between the database servers in the VM Cluster. This ensures that the network traffic of each VM cluster is isolated from the others, and it prevents unauthorized access to the data or resources of other VM clusters. Secure Fabric isolation can also be used for other purposes such as client networking, Data Guard traffic, but it's mainly used to provide security and isolation between multiple tenants or VM clusters.

According to Oracle’s documentation1, Exadata Secure RDMA Fabric Isolation is a feature that enables strict network isolation for Oracle Real Application Clusters (Oracle RAC) clusters on Exadata Database Machine systems that use RDMA over Converged Ethernet (RoCE). Exadata Secure RDMA Fabric Isolation uses RoCE VLANs to ensure that network packets from one VM cluster cannot be seen by another VM cluster. VLAN tag enforcement is done at the KVM host level, which means that security cannot be bypassed by any software exploits or misconfiguration on the database server VMs1.

Therefore, the statement that is true about how Exadata Secure RDMA Fabric isolation is used in X9M-2 with virtualization enabled is:

With Secure Fabric isolation, each Database VM cluster uses a dedicated network partition and VLAN ID for cluster networking between the database servers in the VM Cluster. This provides security and isolation between multiple tenants or VM clusters.

In order for an Exadata X9M-2 Elastic Rack to be installed, two power feeds are required for each of the three-phase 24kVA PDUs. A single cable from each PDU will not be enough to power the rack, and neither a splitter cable nor rearrangement of the power cables from the servers to the PDUs will be able to provide sufficient power for the system. Therefore, the installation cannot proceed until two power feeds are available per PDU.

For more information about power requirements for Exadata X9M-2 Elastic Racks, refer to the Oracle Exadata Database Machine X9M Implementation Essentials official text book and resources.

Search results: [1] Oracle Exadata Database Machine X9M-2 Full Rack Installation - Oracle Docs [2] Exadata Database Machine X8M-2 Mid-Size Rack Installation - Oracle Docs

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmin/exadata-site-requirements.html

It collects configuration information automatically (B). OCM gathers detailed configuration information about a variety of designated Oracle products and components across an enterprise on a regular basis2.

It collects configuration information on demand ©. OCM can also collect configuration information manually when requested by the user or by Oracle Support2.

Collected configuration information can be uploaded automatically to Oracle (E). OCM can upload the collected configuration information to My Oracle Support automatically for analysis and support purposes3.

In the Exadata X9M-2 configuration:

High Capacity (HC) Storage Server: Each HC storage server is equipped with 4 x 6.4 TB NVMe flash cards. These flash cards serve as a cache layer to accelerate I/O performance, especially for read-heavy and mixed workload environments. This configuration combines large storage capacity with NVMe flash for optimal data processing.

Extreme Flash (EF) Storage Server: Each EF storage server contains 8 x 6.4 TB NVMe flash cards, which provides extremely high IOPS and low latency. This configuration is designed for applications demanding high-performance flash storage, making it suitable for intensive OLTP and analytical workloads.

Database Server Flash Storage: The Exadata X9M-2 database servers themselves do not include flash storage as part of their default configuration, which aligns with option D. However, since option E is correct, we do not include D as the other correct answer​​.

To determine the amount of Smart Scan activity on an Exadata Database Machine, you can access two specific commands:

CELLCLI Command: Using the list activerequest command within CELLCLI on all storage cells will show the number of Smart Scans being processed. CELLCLI is an interface specific to Exadata Storage Servers for management and monitoring, and it provides real-time visibility into ongoing Smart Scan operations .

EXACLI Command: Similarly, the list ACTIVEREQUEST command using EXACLI on all storage cells also lists the Smart Scans executed across the storage servers. EXACLI is a remote command-line utility that can be run from a database server to manage storage cells, offering convenient access to similar Smart Scan information .

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

https://docs.oracle.com/en/database/oracle/oracle-database/21/ladbi/db-on-exadata.html