1z0-902 Dumps with Practice Exam Questions Answers

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.

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.

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

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-

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.