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.

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.

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

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.

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.

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.

High availability for the CRM service

Load balancing of connection requests across all six database instances

High availability for the ERP service

Load balancing of client connection requests for CRM across four Single Client Access Name (SCAN) listeners

Load balancing of connection requests for ERP across all database instances running on servers in the prod pool

Load balancing of client connection requests for ERP across three Single Client Access Name (SCAN) listeners

Load balancing of connection requests for CRM across all database instances running on servers in the prod pool

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.

Transparent Application Failover (TAF) using Fast Application Notification (FAN)

Transparent Application Failover (TAF)

Fast Connection Failover (FCF)

Fast Connection Failover (FCF) with Transparent Application Failover (TAF)

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.