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

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