Characteristics of a Database Clustering with RAC and Data Guard Standby Database Deployment

Not Oracle Cloud InfrastructureNot Oracle Cloud at Customer This topic does not apply to Oracle Cloud Infrastructure or to Oracle Cloud at Customer.

This section provides information about the content and configuration of a newly created Oracle Database Cloud Service database deployment that the Oracle Database Cloud Service service level and the Database Clustering with RAC and Data Guard Standby database type.

When you create a database deployment using the Oracle Database Cloud Service service level and choose the Database Clustering with RAC and Data Guard Standby, Database Cloud Service creates two two-node cluster databases using Oracle RAC, one acting as the primary database and one acting as a physical standby database in an Oracle Data Guard configuration. Each node of each cluster database is housed on a compute node that Database Cloud Service creates using Oracle Compute Cloud Service resources. In brief, Database Cloud Service:

  • Creates four compute nodes that are alike in all respects except that each one has its own public IP address.

  • Installs Oracle Linux 6.6, Oracle Grid Infrastructure 18, 12.2.0.1 or 12.1.0.2 (depending on which database version was selected), Oracle Database 18, 12.2.0.1, 12.1.0.2 or 11.2.0.4 (depending on which version was selected), and cloud tooling software on each of the compute nodes.

  • For each cluster database, creates three Oracle Automatic Storage Management (ASM) disk groups to provide shared storage for database data, the fast recovery area, and the redo logs, and mounts the disk groups as shared file systems on the two compute nodes of the cluster using Oracle ASM Cluster File System (ACFS).

  • Creates Oracle Compute Cloud Service networking resources to provide access to the compute nodes, setting all except SSH access on port 22 to a disabled status.

  • Creates two two-node Oracle RAC databases on the compute nodes and starts the network listeners for the nodes.

  • Configures one cluster database as an Oracle Data Guard primary database.

  • Configures the other cluster as an Oracle Data Guard physical standby database.

  • Starts the databases and the network listeners for the nodes.

The following topics provide more detail about this configuration: