1z0-078 Exam Dumps - Oracle Database 19c: RAC, ASM, and Grid Infrastructure Administration

crsctl stop cluster

crsctl config crs

crsctl disable crs

crsctl stop crs

The disk group compatibility attribute for advm must be set to 12. l or higher.

The parent snapshot must be read-only.

The underlying advm volume must be configured with high redundancy.

The parent snapshot must be read/write.

It fails to resize voli because it must be executed as a user belonging to the sysasm group.

It fails to resize the filesystem because it must be unmounted before resizing.

It succeeds but leaves the file system unmounted.

It resizes voli.

It resizes the filesystem mounted on /u01/app/grid/acfsmount.

Global Enqueues and Instance Locks replace mutexes completely in RAC database instances.

Global Enqueues may have converters and waiters in the same instance.

Global Enqueues may have owners and waiters in the same instance.

Global Enqueues and Instance Locks replace latches completely in RAC database instances.

In a RAC database, there is no LMDO process if only one instance is running.

In a RAC One Node database, there is no LMD) process if only one instance is running.

Update the path environment variable on each cluster node to point to the 50RACLE HOME/OPacch directory

Stage the patch on the cluster node where the OPacch utility will be executed.

Update the path environment variable on the node where you will run the OPatch utility to point to the SORacle HOME/OPacch directory.

Stage the patch on all cluster nodes.

The DB_CREATE_FILE_DEST parameter must be set to +DATA(newtemplate).

newtemplate must be defined for the +DATA disk group.

Existing data files in TBS1 must also use the same template.

User-defined subdirectories ORCL and USERS must already exist.

The +DATA disk group should not be part of Flex ASM.

Data files, redo logs, and RMAN backup pieces must be stored in different ASM disk groups for optimal performance.

All ASM Disks belonging to a disk group should be of the same size for optimal performance.

Hardware-based mirroring combined with ASM mirroring guarantees optimal performance.

All ASM Disks belonging to a disk group should have the same hardware specifications and storage attributes for optimal performance.

To improve performance a database must have two disk groups; one for data and one for the fast recovery area.

acfsutil audit read marks audit files to indicate that it is safe to purge them.

acfsutil audit init must be run by a system administrator.

acfsutil audit purge can be run by an audit manager.

Audit information gathered by each cluster node can be consolidated into the unified ACFS audit trail.

acfsutil audit archive must be used to archive audit files that are larger than 10 MB.

The clusterware log files are stored inside the Grid Infrastructure Management Repository database used by the cluster health monitor

The diagcolleccion.pl script must be run from the Grid home directory as the arid infrastructure owner.

There is one ologgerd service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

The oclumon utility may be used to get and set parameters for the cluster health monitor (CHM) repository.

There is one osysmond service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

ASM Cluster File System (ACFS) can be deployed on any nodes.

A database instance on a node can be a client of an ASM instance running on any node.

A database instance on a node cannot be a client of an ASM instance running on other nodes.

A database instance on a node can only be a client of an ASM instance running on the same node.

A database instance on a node uses an ASM instance as an I/O server when requesting I/O to diskgroups.

An ASM instance and database instances can coexist on the same node.

Oracle RAC affinity for partitioned tables routes all database requests for a partition tables to a single Oracle RAC instance leading to higher Oracle RAC performance and scalability because of improved cache locality and reduced internode synchronization and block pings of the partition tables.

Oracle RAC affinity for partitioned tables routes database requests to Oracle RAC instances in such a way that each instance always gets requests for a disjoint subset of rows in the database, this affinity leads to higher Oracle RAC performance and scalability because of improved cache locality and reduced internode synchronization and block pings.

Oracle RAC affinity for partitioned tables routes database requests to all available Oracle RAC instances evenly to create a global affinity in such a way that each instance always gets an even number of requests leading to higher Oracle RAC performance by using a higher levels of available global cache to reduce global resource contention.

To enhance the performance of distributed transactions with applications server that provides XA affinity, you can automatically spawn new dedicated database RAC instances to isolate distributed transaction.

To enhance the performance of distributed transactions with applications server that provides XA affinity, you can direct all branches of a distributed transaction to a single instance in the cluster to improve cache locality and reduce internode synchronization and block pings.

Any database instance with the COMPATIBLE parameter set to 12.2 or later can access it.

It can contain ASM Dynamic Volume Manager (ADVM) volumes.

Each disk in each of the three fail groups is a mirror of the corresponding disk of the other two failure groups.

The ASM compatible attributes can be changed to 12. l for this disk group.

Files created in this disk group always have two copies for each allocation unit: one primary and one secondary.

Cluster resources running on the failed node must be recovered when the node is restarted.

Cluster Resources running on the failed node are relocated to one or more surviving hub nodes.

Cluster Resources running on the failed node are suspended until the node is restarted.

Sessions connected to the failed node could be relocated to one or more surviving nodes.

The node is evicted from the cluster

When a policy is activated, resources can be automatically stopped to comply with the policy definition.

An administrator-defined policy may be activated using the srvctl utility.

When a policy is first created, it is initially inactive.

When a policy is first created, it is initially active.

When a policy is activated, resources cannot be automatically started to comply with the policy definition.

When a policy is activated, nodes may be reassigned to server pools based on the policy definition.

They listen only for database instances on the same node.

They listen on behalf of any ASM instance and all database instances on the same node.

They listen only for the ASM instance on the same node.

There can be only one node listener per node.

They run from the Grid Infrastructure home by default.

Run the crsctl unpin css - host04 command as root on host01, or on either host02 or host03.

Run the crsctl delete node -n host04 command as root on host04.

Run the crsctl delete node -n host04 command as root on host01, or on either host02 or host03.

Run the crsct1 unpin css - host04 command as root on host04.

Run the rootcrs.pl -deconfig -force command as root on host04.

Run the rootcrs.pl -deconfig -force command as root on host01, or on either host02 or host03.

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

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

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

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.

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

The upgrade must be done out-of-place.

When possible, clients with the samecolocation_tagare routed to the same instance that offers a given service.

When possible, clients with the samecolocation_tagare routed to the same available instance even if a preferred instance is available.

When possible, clients with the samecolocation_tagcould be routed across a set of preferred instances based on a specific load balancing option.

When possible, clients with the samecolocation_tagare routed to the same available instance when a preferred instance is not available.

The ACFS file system will be permanently removed from the volume.

The ACFS mount registry with Oracle restart is automatically deleted.

The disabling of volume does not destroy data in the file system.

The volume can be enabled and the file system can be mounted back again to access the existing data.

The ACFS file system will be permanently removed from the volume only if the file system is empty.

SSH user equivalence for the Oracle user can be set up before the software installation.

Fix-up scripts generated during the installation must be run as root on UNIX platforms.

The software must be installed into a local file system on each node.

The software must be installed into a cluster file system.

RAC installations require Oracle Enterprise Edition.

The software can be installed into an ACFS file system.

The software must be installed on all nodes in the cluster.