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

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 .

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.

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.

According to the Oracle Exadata Database Machine documentation12, two recommended configuration best practices for backup and recovery on Exadata are:

A. Placing the backup network on dedicated switches installed in the top of the rack (ToR) has the benefits of isolating the backup network from other workloads and providing a greater level of control.

D. When off-site long-term backup retention is needed, use Oracle Database Backup Cloud Service as a low-cost, offsite scalable storage for a disaster recovery solution.

According to Oracle’s documentation1, one of the utilities for diagnostics and repair of Oracle Exadata Storage Server is ExaWatcher, which collects operating system and network metrics on database servers and storage servers. The utility is located in the /opt/oracle.ExaWatcher directory1.

To investigate why an Exadata Database Server stopped communicating on the client network for 10 minutes over the past weekend, you can use the GetExaWatcherResults.sh script to collect and analyze ExaWatcher data for a specified time range1.

Therefore, the command that you should use to investigate this is:

/opt/oracle.ExaWatcher/GetExaWatcherResults.sh —from _17:00:00 —to _23:59:00

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

The steps and the order in which they should be executed to create an ACFS Filesystem for use as a staging area for data loads are:

asmcrad volcreate -G data -s 1024G acfs_dataload_vol : This command creates a new volume in the data diskgroup, with a size of 1024 GB, and named acfs_dataload_vol.

asmcmd vol info -G data acfs_dataload_vol | grep Device: This command will show the device name of the newly created volume

/usr/sbin/mkfs -t acfs /dev/asm/ac:fs_dataload_vol-123: This command creates a new ACFS filesystem on the volume created in step 1

sudo /u01/app/19.0.0.0/grid/bin/srvctl start filesystem -device /dev/asn/acfs_dataload_vol-123: This command starts the filesystem created in step 3

sudo chovn -R oracle:dba /mnt/acfs_dataload_vol: This command changes the ownership of the /mnt/acfs_dataload_vol to the oracle:dba user.

/sbin/acfsutil snap create -v data_load /mnt/acfs_dataload_vol: This command creates a snapshot of the filesystem to be used as a staging area.

acfsutil size +2S0G -d /dev/asm/acfs_dataload_vol-123 /mnt/acfs_dataload_vol/ : This command increases the size of the filesystem by 2GB

/u01/app/19-G.O-Q7grid/bin/srvctl add filesystem -device /dev/asm/acfs_dataload_vol-

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 .

According to Oracle.com documents or resources, the three options that are available for database consolidation on Exadata are:

A. Multiple pluggable databases in one or more container databases on a Virtual Machine or Bare Metal cluster123.

C. A single database with one or more schema per application12.

E. Multiple Databases on a cluster12.

https://blogs.oracle.com/exadata/post/database-consolidation-why-and-how