Oracle 1Z0-070 Exam Dumps

You must retain the index and make it visible again for the constraint to be recognized
and enforced.

You must retain the index and set the constraint to DISABLE NOVALIDATE RELY for
the constraint to be recognized.

B: 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.
C: DISABLE NOVALIDATE RELY means: "I don't want an index and constraint 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 constraints) and forget about it.

A maximum of eight table columns for any table are indexed per storage region.

The use of Storage Indexes for a particular database can be disabled by using an I/O
Resource Manager Database Plan.

A Storage Index is automatically maintained by CELLSRV based on the filter columns of
the offloaded SQL.

A: Each disk in the Exadata storage cell is divided into equal sized pieces called storage
regions (default 1MB). There is an index entry for every storage regions (1MB of data
stored on disk). Each entry contains the minimum and maximum value for columns seen in
‘where’ clause predicates. Information for up to 8 columns can be stored. The index is then
used to eliminate disk IO by identifying which storage regions don’t match the ‘where’
clause of a query

The database server ILOMs must have SNMP traps configured to use the management
network for notifications to ASR Manager.

The storage server ILOMs must have SNMP traps configured to use the management
network for notifications to ASR Manager.

B: Database Server ILOM plug-in
Monitoring 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.
C: Exadata Storage Server plug-inextends 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.
References:
https://dbatrain.wordpress.com/2011/06/
http://docs.oracle.com/cd/E21659_01/html/E21660/z40015671004046509.html