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

All server pools in a cluster are controlled by the policy set, when user-defined policy management is used.

Clusterware administrators cannot directly modify the policy set when Quality of Service (QoS) Management is used.

A server pool can have different attributes defined for different policies in the policy set, when user-defined policy management is used.

A server pool can have the same attributes defined for different policies in the policy set, when user-defined policy management is used.

Servers in a server pool outside the control of the policy set are never affected by policy changes, when user-defined policy management is used.

Oracle RAC Resource Management only allows assignment of the SGA during instance startup.

Oracle RAC Resource Management requires the same SGA value for all the instances of a RAC database which is configured during database startup only.

Oracle RAC Resource Runtime Management allows for automatic and runtime adjustment of the SGA.

Oracle RAC Resource Management only allows assignment of the SGA during database startup.

Each cluster node must have at least two network interface cards.

You must enable the Name Server Cache Daemon

A DHCP service on the private network for the cluster is required to allocate virtual IP addresses for HAIP.

A DHCP service on the public network for the cluster is required to allocate virtual IP addresses as required by the cluster.

DNS must be configured to delegate name resolution for the cluster subdomain to the cluster.

You must create a Grid Management Repository database.

an application VIP

A Server Pool

a resource dependency definition

an application resource

a script agent

A server pool must be created with srvct1 before creating a policy-managed RAC database that uses that server pool for a service.

They can be policy managed for a multitenant database.

Policy-managed services specified for a database allow the creation of a new server pool using dbca.

They can be administrator managed for a multitenant database.

Singleton services are not permitted for multitenant databases.

Use srvctl start vip to start the VIP on host01.

Use oifcfg setif to start the VIP on host01.

Use oifcfg setif to stop the VIP on host01.

Use srvctl modify nodeapps to change the VIP on host01.

Use srvctl stop vip to stop the VIP on host01.

2 = NORMAL, 3 = TRANSACTIONAL, 1 = ABORT

2 = NORMAL, 3 = IMMEDIATE, 1 = ABORT

3 = NORMAL, 2 = TRANSACTIONAL, 1 = ABORT

3 = NORMAL, 2 = ABORT, 1 = IMMEDIATE

3 = NORMAL, 2 = IMMEDIATE, 1 = ABORT

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.

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.

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.

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 maximum value of ASM_POWER_LIMIT is 1024.

The default value of INSTANCE_TYPE is ASM.

A change to ASM_DISKSTRING requires a restart of all ASM instances for the change to take effect.

The ASM_DISKGOUPS parameter is optional.

ASM_POWER_LIMIT controls the number of RDBMS instances that can access a disk group while it is being rebalanced.

Database block buffers

Mutexes

Redo log buffers

Latches

Enqueues

Cursors

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

The Oracle Clusterware stack is stopped on all nodes.

The Oracle Clusterware stack is prevented from being automatically started on host01.

The Oracle Clusterware stack is prevented from being automatically started on all nodes.

The Oracle Clusterware stack is stopped on all nodes except host01.

The Oracle Clusterware stack is started on all nodes except host01.

The Oracle Clusterware stack is started on all nodes.

exec sys.dbms shared pool.keep('SEQ1','Q'>

alter sequence seal cache 10000;

alter sequence seql noorder;

alter sequence seql keep;

alter sequence seql order;

Different nodes in a cluster may belong to separate administrator-defined categories.

All nodes in a cluster belong to the same Oracle-supplied category.

A server may be added to only one category using the crsctl utility.

All server attributes that may be used to determine the server category are discovered automatically by Oracle Clusterware.

All server attributes used for categorization are administrator modifiable.

Server categories can only be used for nodes running an application server.

They can be applied in-place.

When performing rolling patches, the vips for the node being patched are relocated to another node.

Some Grid Infrastructure patchsets may not be intalled in a rolling fashion.

When performing rolling patches,crsctl query crs softwareversionalways displays the earliest version of the software running anywhere in the cluster.

The Grid Infrastructure Management Repository is only required when using ASM.

Specifying the use of Grid Naming Service is optional.

Normal Redundancy ASM Disk Groups used for Clusterware files will contain three voting files regardless of the number of

The Clusterware binaries may be installed without installing ASM binaries.

High Redundancy ASM Disk Groups used for Clusterware files will contain two OCRs.

an 0/S user to own the Oracle Database installation

an O/S group called dba

an O/S user to own the Grid Infrastructure installation

an O/S group to own the software inventory

A group to own Automatic Storage Management (ASM) Filter Driver-provisioned storage

an O/S user to own the Clusterware installation and a different O/S user own the Automatic Storage Management (ASM) installation