1. Administering Oracle Database Classic Cloud Service
  2. Configuring Database Features, Database Options, and Companion Products
  3. Using Oracle Real Application Clusters (RAC) and Oracle Data Guard Together in Database Classic Cloud Service

Using Oracle Real Application Clusters (RAC) and Oracle Data Guard Together in Database Classic Cloud Service

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

When creating a database deployment on Oracle Database Classic Cloud Service, you can create a pair of Oracle RAC databases linked together as the primary and standby databases of an Oracle Data Guard configuration.

Note:

Oracle Database Classic Cloud Service does not currently include the fast-start failover (FSFO) feature of Oracle Data Guard. In Database Classic Cloud Service, you perform failover operations manually, as described in Performing a Manual Failover Operation.

To create a Database Classic Cloud Service database deployment that uses Oracle Real Application Clusters (Oracle RAC) and Oracle Data Guard, make the following choices in the Create Instance wizard:

  • For Software Edition, choose Enterprise Edition - Extreme Performance.

  • For Database Type, choose Database Clustering with RAC and Data Guard Standby.

  • For Compute Shape (on the Instance Details page), choose a shape with two or more OCPUs.

  • For Standby Database Configuration (on the Instance Details page), choose where you want the standby database placed in relation to the primary database:

    • High Availability—The standby database is placed in a different availability domain from the primary database, thus providing isolation at the infrastructure level.

    • Disaster Recovery—The standby database is placed in a different data center from the primary database, thus providing isolation at the infrastructure level and geographical separation to support availability despite catastrophic events.

When you make these choices, Database Classic 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. In each cluster database, the two cluster nodes share data, fast recovery area, and redo log storage. Database Classic Cloud Service creates these compute nodes using computing, storage and networking resources provided by Oracle Cloud Infrastructure Compute Classic.

Because the Software Edition is Enterprise Edition - Extreme Performance, the deployment includes Oracle Active Data Guard. For information on the real-time query and the automatic block media recovery features of Oracle Active Data Guard, see "Opening a Physical Standby Database" in Oracle Data Guard Concepts and Administration for Release 18, 12.2, 12.1 or 11.2.

More About a Deployment that Uses Oracle RAC and Oracle Data Guard Together

  • Cluster size: currently, the Oracle RAC database on a Database Classic Cloud Service deployment is limited to a two-node cluster.

  • Cloud tooling: Oracle Cloud tooling is provided for the common administrative tasks of scaling, backing up and recovering, and patching. For more information, see The raccli Utility.

  • Data Guard operations: to perform operations such as switchover, failover and reinstate, you can use the Oracle Database Classic Cloud Service console or you can use subcommands of the raccli utility. For information, see Administering a Data Guard Configuration and The raccli Utility.

  • Updating passwords: use the raccli update databasepassword command to update the password in the keystore (wallet) and to update the password for database users.

  • Network access: on the compute nodes, access to all ports except port 22 is disabled. Port 22 is open for passwordless, key-based SSH access by the opc user. To enable access to other ports, see Enabling Access to a Compute Node Port.

  • Networking for client access: to make client connections to one of the Oracle RAC databases, you include particular options in the connection’s entry in the client’s tnsnames.ora file. For more information, see Connecting Remotely to the Database by Using Oracle Net Services.

  • Database file storage: for each Oracle RAC database, storage for database data files, the fast recovery area, and the redo logs is created and managed using Oracle Automatic Storage Management (ASM) and Oracle Automatic Storage Management Cluster File System (ACFS) instead of Linux LVM.

  • Included software: Oracle Application Express, Oracle REST Data Services, and Oracle SQL Developer Web are not currently included.

For more detailed information, see Characteristics of a Database Clustering with RAC and Data Guard Standby Database Deployment.