Download Oracle Exadata X5 Administration.1z0-070.ExamLabs.2019-12-10.54q.vcex

You can manage I/O resources based on categories by creating a category plan. You can add any number of categories, or modify the predefined categories. You should map consumer groups to the appropriate category for all databases that use the same cell storage. Any consumer group without an explicitly specified category defaults to the OTHER category. References: http://docs.oracle.com/cd/E80920_01/SAGUG/exadata-storage-server-iorm.htm

B: You can configure SNMP Trap Destinations for the Exadata Storage Servers with the following command:# cellcli -e “alter cell snmpSubscriber=(host ='ASR-Manager-name-or-IP-address',port=162,community=public,type=asr)” D:  Exadata Storage Server plug-inThis extends the monitoring of exadata cells in addition to providing a GUI interface. The plug-in uses an SSH connection to the cellmonitor user on the cells and uses list commands only. This is for interactive monitoring. One may also set thresholds using the plug-in which are distinct from any thresholds set using cellcli utility as the celladmin user. For alerts to be sent to the plug-in, SNMP traps are used as follows:Cell ILOM alerts are sent to the cell Management Server (MS) via an SNMP trap. The MS then send SNMP notifications onward to the plug-in. Cell alerts flagged by MS itself, such as cell thresholds being exceeded, or ADR software alerts, are sent to the plug-in using SNMP. E: Database Server ILOM plug-inMonitoring databases and their instances, ASM environments, the Grid Infrastructure, and the host software environment are done by Enterprise Manager in the usual way as these are standard targets. But monitoring the hardware for the database servers requires the ILOM plug-in, as there is no Management Server (MS) on the database servers to receive SNMP traps from the ILOM. The plug-in will receive sensor state and availability data from the ILOM including alerts based on pre-set ILOM thresholds. References:https://dbatrain.wordpress.com/2011/06/http://docs.oracle.com/cd/E21659_01/html/E21660/z40015671004046509.html

AB: Oracle recommends that you install Oracle ASR Manager on an external, standalone server. This server receives fault telemetry information from Oracle Exadata Database Machine servers. This server must run an Oracle Solaris or Linux operating system.G: Before installing Oracle Auto Service Request (Oracle ASR) you must ensure connectivity to the Internet using HTTPS.References: Oracle Auto Service Request Exadata Database Machine Quick Installation Guidehttp://docs.oracle.com/cd/E80920_01/ASXQI/toc.htm#GUID-89192315-1B1A-4B5A-89BB-94BB5B6ABB05

The first two disks of Exadata Storage Server are system disks. Oracle Exadata Storage Server Software system software resides on a portion of each of the system disks. These portions on both system disks are referred to as the system area. The default configuration on Exadata is to have 3 diskgroups - DATA, RECO, and DBFS_DG.

Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group. Example: View the space currently used by the disk groups.SELECT name, total_mb, free_mb, total_mb - free_mb used_mb, round(100*free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1;     The example above shows that the DATAC1 disk group has only about 15% of free space available while the RECOC1 disk group has about 87% free disk space. The PCT_FREE displayed here is raw free space, not usable free space. Additional space is needed for rebalancing operations. References: http://docs.oracle.com/cd/E80920_01/SAGUG/exadata-administering-asm.htm#SAGUG20526

B: Migrated Rows is a special case of chained rows. Migrated rows still affect performance, as they do in conventional storage situations, but with the additional overhead of reducing the beneficial effects of “Smart Scan” in addition to increasing the number of I/OsE: Smart Scans - broadly speaking and ignoring edge cases - can only transport a maximum of 254 columns from a single (non-HCC) segment. Requesting more columns will simply disable Smart Scans for that segment.An interesting limitation to Exadata Smart Scans - if more than 254 columns from a table (not HCC compressed, more on that in moment) need to be projected, Smart Scans for that particular segment will be disabled and Exadata will fall back to conventional I/O. This means that the number of columns in the projection clause can make a significant difference to performance, since only Smart Scans allow taking advantage of offloading and particularly avoiding I/O via Storage Indexes. Incorrect Answers:A: Smart scan can cope with some cases of chained rowsReferences: http://oracle-randolf.blogspot.se/2013/01/exadata-smart-scan-projection-limitation.html

On both physical and virtual deployments, Exadata systems use minimal Linux distributions to ensure that just the RPMs needed to run Oracle database, are installed and enabled. References: http://www.oracle.com/technetwork/database/exadata/exadata-x5-2-ds-2406241.pdf

D: With Exadata storage, database operations are handled much more efficiently. Queries that perform table scans can be processed within Exadata storage with only the required subset of data returned to the database server. Row filtering, column filtering and some join processing (among other functions) are performed within the Exadata storage cells. When this takes place only the relevant and required data is returned to the database server.E: With Smart Scan processing, row filtering, column filtering, some join processing, and other functions are performed in the Exadata cells.References: http://www.centroid.com/blog/exadata-smart-scan-processing