Regenerate Oracle Exadata Database Machine Administration, Software Release 11.x 1Z0-027 Test Question

None

cellip.ora
The cellip.ora is the configuration file, on every compute node, that tells ASM instances which cells are available to this cluster.
Here is a content of a typical cellip.ora file for a quarter rack system:
$ cat /etc/oracle/cell/network-config/cellip.ora cell="192.168.10.3"
cell="192.168.10.4" cell="192.168.10.5"
Now that we see what is in the cellip.ora, the grid disk path, in the examples above, should make more sense.
Note:
* cellinit.ora decides which network takes storage traffic.
* cellip.ora - list of cells, new cells can be added dynamically without shutdown

None

B: * Grid disks (the logical disks
that reside on physical cell disks) are created on these flash-based cell disks and the grid disks are assigned to an Automatic Storage Management (ASM) diskgroup. The best practice would be to reserve the same amount of flash on each Exadata cell for flash disks and have the ASM
diskgroup spread evenly across the Exadata cells in the configuration just as you would do for
regular Exadata grid disks. This will evenly distribute the flash I/O load across the Exadata cells
and flash.
Note:
* The Exadata
Storage Server comes with a substantial amount of flash storage. A small amount is allocated for
database logging and the remainder will be used for caching user data

None

A CTAS (Create table as select) will always use direct path (B, not C) load but IAS (Insert as select) statement will not. In order to achieve direct path load with an IAS statement you must add the APPEND hint to the command (A, not D).
Direct path loads can also run in parallel. You can set the parallel degree for a direct path load
either by adding the PARALLEL hint to the CTAS or IAS statement or by setting the
PARALLEL clause on both the external table and the table into which the data will be loaded.
Once the parallel degree has been set at CTAS will automatically do direct path load in parallel
but an IAS will not. In order to enable an IAS to do direct path load in parallel you must alter the session to enable parallel DML.
Note:
* Parallel Direct Path Load
The key to good load performance is to use direct path loads wherever possible. A direct path
load parses the input data according to the description given in the external table definition,
converts the data for each input field to its corresponding Oracle data type, then builds a column
array structure for the data. These column array structures are used to format Oracle data blocks
and build index keys. The newly formatted database blocks are then written directly to the database, bypassing the standard SQL processing engine and the database buffer cache.
Reference: Best Practices for Implementing a Data Warehouse on the Oracle Exadata Database Machine; Using CTAS & Exchange Partition Replace IAS for Copying Partition on Exadata

http://docs.oracle.com/cd/E17559_01/install.111/e20085/e20085-03.htm

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

Note:
* The following prerequisites must be met before you can deploy the plug-in:
* Set and validate the preferred credentials on all Agents where you want to deploy the plug- in. This is essential in order to deploy the plug-in.
The PDU firmware version must be 1.02 or later.
* This plug-in will be used to monitor PDU\'s actual current value of Phase1, Phase2, and Phase3 and raises appropriate events if they have crossed the different threshold values. Each PDU will have a plug-in instance added to its own OEM Grid Control agent.
By deploying the plug-in to your Grid Control environment, you gain the following management features:
Monitor PDU targets.
Raise alerts and violations based on thresholds set on monitoring and configuration data. Provide rich out-of-box metrics and reports based on the gather
Reference: Oracle Enterprise Manager System Monitoring Plug-In Installation Guide for
Exadata Power Distribution Unit

A: Before installing ASR, please ensure the following conditions are met:
/ (A) Ensure connectivity to the Internet using HTTPS.
/ Make sure you have access to My Oracle Support and that your contact information is
correct and current.
/ Make sure all of your assets have a Contact assigned and that the contact is correct and current.
/ Identify and designate a system to serve as ASR Manager.
/ Identify and verify ASR assets.
F, G (not C, not E, not B): The recommended configuration is to install the ASR Manager, which receives fault telemetry information from the servers in Oracle Exadata Database Machine, on an external standalone server. This server must run Solaris or Linux as the operating system.
Reference: Oracle Auto Service Request Exadata Database Machine Quick Installation Guide

/B: Step 1:
Run the following command to check if there are other offline disks
CellCLI> LIST GRIDDISK ATTRIBUTES name WHERE asmdeactivationoutcome != \'Yes\'
If any grid disks are returned, then it is not safe to take the storage server offline because proper Oracle ASM disk group redundancy will not be intact.
/C: Step 2:
Inactivate all the grid disks when Oracle Exadata Storage Server is safe to take offline using the following command:
CellCLI> ALTER GRIDDISK ALL INACTIVE
Taking the storage server offline when one or more grid disks are in this state will cause Oracle ASM to dismount the affected disk group, causing the databases to shut down abruptly.
/D: Step 3:
-- Verify all grid disks are INACTIVE to allow safe storage server shut down by running the following command:CellCLI> LIST GRIDDISK ATTRIBUTES name, asmmodestatusCellCLI> LIST GRIDDISKIf all grid disks are INACTIVE, then the storage server can be shutdown without affecting database availability
/E: Step 4:
To stop a server, use the shutdown command. To stop immediately and keep it down, i.e. not reboot, execute:
#
shutdown -h -y now

Note:
* You may have noticed that we introduced Invisible Indexes as an 11g New Feature. Their main benefit is that we can test whether performance differs if we would drop an index without actually dropping it. This is particular useful after an Exadata Migration because we expect that some conventional indexes migrated are now obsolete and may be substituted by Storage Indexes.
* With making indexes invisible, we can easily check whether indexes are useful without having to drop (and in case recreate) them actually. While this may be of interest for “ordinary” Oracle Databases already, it is particular a useful feature for Exadata where we expect some conventional indexes to become obsolete after a migration.
* DISABLE NOVALIDATE RELY means: "I don\'t want an index and constaraint checking to slow down my batch data loading into datawarehouse, but the optimizer can RELY on my data loading routine and assume this constraint is enforced by other mechanism". This information can greatly help optimizer to use correct materialized view when rewriting queries. So if you don\'t use materialized views for query rewrite then you can put RELY for all your constraints (or NORELY for all your constraits) and forget about it.

None

Incorrect:
Not C, Not E: there are both stateful and stateless alerts

None

None

A: In conjunction with Cluster Health Monitor, QoS Management’s Memory Guard detects nodes that are at risk of failure due to
memory over-commitment. It responds by automatically preventing new connections thus preserving existing workloads and restores connectivity once the sufficient memory is again available.
F: The ora.oc4j is for the QoS (Quality of Service Management), which is only available on
Exadata.
Incorrect:
Not B: The Cluster Verification Utility (CVU) performs system checks in preparation for installation, patch updates, or other system changes. Using CVU ensures that you have completed the required system configuration and preinstallation steps so that your Oracle grid infrastructure or Oracle Real Application Clusters (Oracle RAC) installation, update, or patch operation completes successfully.

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.

Reference: Migrating the Oracle E-Business Suite Database to Oracle Exadata Database Machine Using Transportable Tablespaces
Reference: Migrating Oracle E-Business Suite to Oracle Exadata Database Machine Using Oracle Data Pump

Note:
* The ILOM management interface is also integrated with Oracle Enterprise Manager Ops Center.
* ILOM Features and Functionality include: Remote hardware monitoring which include:
Monitor customer-replaceable units (CRUs) and fieldreplaceable units (FRUs), including power supplies, fans, host bus adapters (HBAs), disks, CPUs, memory, and motherboard
* The ILOM-based service processor (SP) receives error telemetry about error events that occur within the major system components on the host (CPU, memory, and I/O hub) and the environmental subsystem within the chassis (such as fans, power supplies, and temperature). The components and conditions are then diagnosed as fault events and captured in the ILOM event log.