The OCRCHECK utility can check the OLR in an online fashion with the clusterware running on all nodes.

The OCRCONFIG utilty can be used to repair a corrupt OCR file in an online fashion with the clusterware running on all nodes.

The CLUVFY utility can check the integrity of the OCR but not the OLR.

The OCRDUMP utility can dump specific keys from the OLR in an online fashion with the clusterware running on all nodes.

The OCRDUMP utility can dump specific keys from the OCR in an online fashion with the clusterware running on all nodes.

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.

Only one GRD shadow resource may exist for an Enqueue Resource.

Shadow GRD resources may exist in more than one database instance for a resource.

Clustered ASM has GRD resources distributed among all ASM instances.

All GRD Enqueue Resource master metadata is held in the large pool of the same database instance.

All GRD Enqueue Resource master metadata is held in the shared pool of the same database instance.

RAC databases have GRD cache resources distributed among all the database instances and stored in the large pool of each instance.

RAC databases have GRD cache resources distributed among all the database instances and stored in the shared pool of each instance.

Replication is automatically terminated if the primary file system has less than 2 GB free space.

ACFS auditing information is replicated from the primary file system to the standby file system.

Standby redo log files are required on the standby site for synchronous redo transport.

The privilege sysrepl has been introduced for ACFS replication.

One site of an ACFS replication configuration can host both primary and standby file systems.

An administrator-managed resource can be started manually using srvct1.

A policy-managed resource can be started manually using crsct1.

An administrator-managed resource can be started manually using crsct1.

The action script is automatically set when using a policy-managed resource.

A policy-managed resource can be started manually using srvct1.

Resource dependencies are automatically set when using a policy-managed resource.

It can manage database services only if they are defined as UNIFORM services.

It requires Oracle Grid Infrastructure for a Cluster to be installed and Clusterware to be running.

A server pool can be managed by QoS even if it does have database instances running on any server in the pool.

Databases managed by QoS can be administrator managed or policy managed.

It supports multiple databases assigned to the same server pool.

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.

Set COMPATIBLE.ASM to 11.2, COMPATIBLE.RDBMS to 12.1, and COMPATIBLE.ADVM to 11.2.

Set COMPATIBLE.ASM to 12.1, COMPATIBLE.RDBMS to 12.1, and COMPATIBLE.ADVM to 12.1.

Set COMPATIBLE.ASM to 11.2, COMPATIBLE.RDBMS to 12.1, and COMPATIBLE.ADVM to 12.1

Set COMPATIBLE.ASM to 12.1, COMPATIBLE.RDBMS to 11.2, and COMPATIBLE.ADVM to 12.1.

Set COMPATIBLE.ASM to 11.2, COMPATIBLE.RDBMS to 11.2, and COMPATIBLE.ADVM to 11.2.

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.

Security for the cluster interconnect is invoked automatically as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c and Database administrators or cluster administrators do not need to make any configuration changes for this feature.

Security for the cluster interconnect is invoked automatically as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c using an auto-generated encryption key that is stored locally on each node of the cluster in an Oracle Wallet and Database administrators or cluster administrators must provide a valid path for the Wallet file.

Security for the cluster interconnect is invoked by auto-generated server certificates that will be assigned to each cluster node as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c.

Database administrators or cluster administrators must provide an encryption key during new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c to secure the interconnect communication.

Database administrators or cluster administrators must provide a valid server certificate and an Oracle Wallet for each node during new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c to secure the interconnect communication.

Using the rconfig utility to migrate the database to shared storage and then using dbca to start one or more RAC database instances on the cluster

Using dbca to migrate the database to shared storage and then to start one or more RAC database instances on the cluster

Using the rconfig utility to create a template from the single-instance database and then using dbca to create a RAC database on the cluster using that template

Using dbca to create a template from the single-instance database and then to create a RAC database on the cluster using that template

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.

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.

HANFS provides high availability in case of an NFS client failure.

HANFS' performance depends on the characteristics of the underlying ASM disks.

HANFS does not depend on NFS services provided by the underlying operating system.

HANFS provides high availability in case of cluster node failure.

NFS client requests are distributed by DNS in a round-robin fashion to the cluster nodes that export the NFS

One undo tablespace for each pdb is required.

PDBs can have local temporary

You can open one, several, or all PD3s on one, several, or all cdb instances.

It requires the cdb to use shared undo management.

One undo tablespace for each instance is required.

PDBs must use shared Temporary

Database instances perform read I/O using an ASM instance as an I/O Server.

Database instances can write metadata to ASM diskgroups.

Database instances perform read I/O directly to ASM Disks.

ASM instances can write metadata to ASM diskgroups.

If a database instance writes to an ASM-based datafile whose redundancy attribute is set to mirror, then the ASM instance writes the mirror copy

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.

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.

It can analyze performance over any given time period.

It can diagnose skew in response time.

It can analyze performance using data captured on all instances.

It can only analyze performance on the instance running the ADDM job.

It can diagnose latency problems in the Cluster Interconnect.

It runs automatically in Instance ADDM mode after each AWR snapshot is created.

The service must be manually started withSRVCTLafter a planned restart of the instance hosting the service.

The service must be manually restarted withSRVCTLevery time the instance hosting the service fails.

The service must be manually restarted withSRVCTLafter restarting the Clusterware stack on the node hosting the service.

Clusterware will monitor the service while it is active.

When manually started, the service will always start on one or more available instances rather than on their preferred instances.