Download Oracle Exadata X3 and X4 Administration.1z0-027.CertDumps.2017-12-14.72q.vcex

A: If you want Oracle ASM to mirror files, specify the redundancy level as NORMAL REDUNDANCY (2-way mirroring by default for most file types) or HIGH REDUNDANCY (3-way mirroring for all files). You specify EXTERNAL REDUNDANCY if you do not want mirroring by Oracle ASM. For example, you might choose EXTERNAL REDUNDANCY if you want to use storage array protection features.D: Restoring the redundancy of an Oracle ASM disk group after a transient disk path failure can be time consuming. This is especially true if the recovery process requires rebuilding an entire Oracle ASM failure group. Oracle ASM fast mirror resync significantly reduces the time to resynchronize a failed disk in such situations. When you replace the failed disk, Oracle ASM can quickly resynchronize the Oracle ASM disk extents.To use this feature, the disk group compatibility attributes must be set to 11.1 or higher. Incorrect:Not C: You can set the DISK_REPAIR_TIME disk group attribute to delay the drop operation by specifying a time interval to repair the disk and bring it back online. Note:* The redundancy levels are:/ External redundancy Oracle ASM does not provide mirroring redundancy and relies on the storage system to provide RAID functionality. Any write error cause a forced dismount of the disk group. All disks must be located to successfully mount the disk group. / Normal redundancy Oracle ASM provides two-way mirroring by default, which means that all files are mirrored so that there are two copies of every extent. A loss of one Oracle ASM disk is tolerated. You can optionally choose three-way or unprotected mirroring. / High redundancy Oracle ASM provides triple mirroring by default. A loss of two Oracle ASM disks in different failure groups is tolerated. Reference: Administering Oracle ASM Disk Groups

To use storage indexes, Oracle Exadata queries must use smart scans, so not all types of applications can benefit from storage indexes. * 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.

A: Configure one RMAN channel per tape drive and add tape drives to scale backup rates.C: Configure the Preferred Network Interface (PNI) to direct the Oracle Secure Backuptraffic over the InfiniBand network interface. Example:ob> lspni (List Preferred Network Interface) mediaserver1:PNI 1:interface: mediaserver1-ibclients: dbnode1, dbnode2, dbnode3, dbnode4, dbnode5, dbnode6, dbnode7, dbnode8 PNI 2:interface: mediaserver1clients: adminserver dbnode1:PNI 1:interface: dbnode1-ibclients: mediaserver1Note:* Using the Sun ZFS Backup Appliance as an Oracle RMAN backup target for an Oracle Exadata system delivers much faster backup and recovery, enabling organizations to achieve shorter recovery time objectives and shrink backup windows. The appliance is designed for high sustained read and write I/O performance, and it is connected to the Oracle Exadata system via a high-throughput InfiniBand network fabric. * As the only unified storage vendor to support InfiniBand as a storage network for backup and restore operations, Oracle is leading the way with native high-bandwidth interconnects.  * The InfiniBand network provides 40 Gb of bandwidth per port between the database servers, storage cells, and the Sun ZFS Backup Appliance. Backup and restore operations can be automatically parallelized across all database nodes, Oracle Exadata storage cells, Sun ZFS Backup Appliance channels, and controllers.

Reference: Oracle Exadata Database Machine - Backup & Recovery Sizing:  Tape Backups

Airflow must be front-to-back. Reference: Oracle White Paper, ORACLE Exadata Database Machine X3-8

There are several techniques for migrating data to a Database Machine. Migration can be done using Oracle Recovery Manager (RMAN) to backup from traditional storage and restore the data onto Exadata. Oracle Data Guard can also be used to facilitate a migration. This is done by first creating a standby database based on Exadata storage. The standby can be using Exadata storage and the production database can be on traditional storage. By executing a fast switchover, taking just seconds, you can transform the standby database into the production database. This provides a built-in safety net as you can undo the migration very gracefully if unforeseen issues arise. Transportable Tablespaces (B) and Data Pump may also be used to migrate to Exadata. Any technique used to move data between Oracle Databases can be used with Exadata.

Note:The Enterprise Manager agent must be deployed to all compute nodes of the Database Machine. Oracle's documentation uses the term compute node when referring to the database server tier of the platform. The Exadata Database Machine runs Oracle Database 11g Real Application Cluster. The cluster and the database run on the servers known as database nodes or compute nodes (or simply “nodes”). Cells and compute nodes are not shared between partitions. Compute nodes in same partition share the same Cluster.