1z0-068 Exam Dumps - Oracle Database 12c: RAC and Grid Infrastructure Administration

The ORACLE_HOME environment variable must be set to the Grid Infrastructure home directory in the installation owner’s environment.

The upgrade must be done in-place.

The upgrade must be done out of place.

Upgrade validation may be done using the Oracle Universal Installer which in turn invokes the built-in cluster verification utility.

The cluster verification utility cluvfy.sh can verify that the cluster is ready for an upgrade.

The ORACLE_SID environment variable must be set to the SID of the ASM instance in the installation owner’s environment.

The cluster verification utility cluvfy.sh can generate fixup scripts to run on all nodes of the cluster.

Files created in it have three copies for each allocation unit.

Any database instance with the COMPATIBLE parameter 10.1 and higher can use it.

The Compatible attribute values of the disk group can be changed to lower values.

Files created using a template with the redundancy attributes set to MIRROR will have three-way Mirroring.

The RECO diskgroup may only be used for the FRA.

Files created using a template with the redundancy attribute set to HIGH will have three-way mirroring. 

Use the cluvfy comp command for the specific resource within a component.

Use the crsctl set trace res “resource_name=debugging_level” command.

Use the crsctl set log res “resource_name=debugging_level2” command.

Set the environment variable _USA_ORA_DEBUG=1 and then stop and restart the resource that requires resource debugging data to be collected.

Leaf nodes evicted from a Flex Cluster always require a reboot.

Hug node eviction results in the reboot of all leaf nodes that were connected to the evicted hub node.

Hub nodes evicted from a Flex Cluster always require a reboot.

Hub node eviction results in the eviction of all leaf nodes that were connected to the evicted hub node.

Cluster Resources on a leaf node that is evicted from a Flex Cluster are relocated, if possible, to another leaf node that is connected to same hub node to which the failed leaf node was connected.

Cluster Resources on a hub node that is evicted from a Flex Cluster are always relocated to a leaf node that was connected to the evicted hub node.

Cluster Resources on a hub node that is evicted from a Flex Cluster are always relocated to another hub node in the cluster.

Partitioning ADVM-managed volumes using fdisk or other utilities on a leaf node is not supported.

An ADVM volume cannot be used as a boot device on a leaf node.

To use ADVM volumes, an ASM proxy instance is not required on a leaf node.

ADVM volumes can be used to store the OCR and voting files to be used by a leaf node.

An ADVM volume cannot be used as the root file system on a leaf node.

To use ADVM volumes on a leaf node, the oraclesacfs, oracleoks, and oracleadvm drivers must be loaded on all hub nodes.

The host name in the tnsnames entry must be changed if nodes are added or removed from the Cluster.

Clients using EZConnect can benefit from connect time load balancing because the tnsnames entry refers to a SCAN listener.

Client connection requests are automatically balanced across all IP addresses defined for the SCAN.

A client connection request is received by a SCAN listener that creates the connection to the least-loaded database instance.

Client connection requests are automatically failed over to another SCAN listener if the chosen SCAN listener is not available.