Procedure

Perform the following steps to enable Data Guard on a DB system by creating a DB system and a database.

1. Open the navigation menu. Select Oracle Database, then select Oracle Base Database Service.
2. Choose the Compartment. A list of DB systems is displayed.
3. In the list of DB systems, click the name of the DB system that contains the database you want to assume the primary role for Data Guard.
4. On the DB System Details page, in the Databases section, click the name of the database you want to make primary.
5. On the Database Details page, in the Resources section, click Data Guard Associations.
6. In the Data Guard Associations section, click Enable Data Guard.
7. On the Enable Data Guard page, create a new peer DB system for the standby by providing the following information.
8. In the Create peer DB system section, provide the following information.
   • Display name: Enter a user-friendly name to help you easily identify the resource. Display name can be changed at any time.
   • Region: Select the region of the new peer DB system. For more information on regions and availability domain, see About Regions and Availability Domains.
   • Availability domain: Select the availability domain of the new peer DB system.
9. Configure shape: The shape determines the type of DB system created and the resources allocated to the system. By default, the same shape as the primary is selected for standby.
   • Ampere A1 shape-based DB systems do not support Data Guard associations with Intel or AMD shape-based DB systems.
10. To specify a shape other than the default, click Change shape, and select an available shape from the list. For a complete list of shapes, see Available Shapes and How It Determines the Resources Allocated.
11. Shape series: Select Ampere, AMD, or Intel processor in the processor group.
    • Ampere: Shapes that use Arm-based Ampere processors. The Ampere shapes are flexible.
    • AMD: Shapes that use current-generation AMD processors. The AMD shapes are flexible.
    • Intel: Standard and optimized shapes that use current-generation Intel processors. Both fixed and flexible Intel shapes are available.
    Note
    
    If you select Ampere A1, AMD E4, AMD E5, or Intel X9 flexible shapes, the memory, network bandwidth, and maximum theoretical IOPS scale proportionally.
12. Configure OCPU: Select the number of OCPUs you want to allocate to this instance. For Ampere A1, AMD E4, AMD E5, and Intel X9 flexible shapes, you can select the number of OCPUs by using the slider in the Number of OCPUs per node field.
    • For Ampere A1 shape, a minimum of 1 OCPU and a maximum of 57 OCPUs can be selected.
    • For AMD E4 and E5 shapes, a minimum of 1 OCPU and a maximum of 64 OCPUs can be selected.
    • For Intel X9 shape, a minimum of 1 OCPU and a maximum of 32 OCPUs can be selected.

    The following resources scale proportionately to the number of OCPUs you selected.

    • Memory (GB): The amount of memory you want to allocate to this instance.
      For Ampere A1, AMD E4, AMD E5, and Intel X9 shapes, the memory will scale proportionally based on the number of OCPUs selected.

      • For Ampere A1 shape, for each OCPU, 8 GB of memory is allocated. A minimum of 8 GB and a maximum of 456 GB of memory is allocated.
      • For AMD E4 and E5 shapes, for each OCPU, 16 GB of memory is allocated. A minimum of 16 GB and a maximum of 1024 GB of memory is allocated.
      • For Intel X9 shape, for each OCPU, 16 GB of memory is allocated. A minimum of 16 GB and a maximum of 512 GB of memory is allocated.
    • Network bandwidth (Gbps): The amount of network bandwidth you want to allocate to this instance.
      For Ampere A1, AMD E4, AMD E5, and Intel X9 shapes, the bandwidth will scale proportionally based on the number of OCPUs selected. For each OCPU, 1 Gbps of network bandwidth is allocated.

      • For Ampere A1 shape, a minimum of 1 Gbps and a maximum of 40 Gbps of network bandwidth is allocated.
      • For AMD E4 and E5 shapes, a minimum of 1 Gbps and a maximum of 40 Gbps of network bandwidth is allocated.
      • For Intel X9 shape, a minimum of 1 Gbps and a maximum of 32 Gbps of network bandwidth is allocated.
    • Theoretical max IOPS: The amount of input and output per second (IOPS) you want to allocate to this instance. Theoretical max IOPS is also dependent on the storage you select.
      For Ampere A1, AMD E4, AMD E5, and Intel X9 shapes, the theoretical max IOPS will scale proportionally based on the number of OCPUs selected. For each OCPU, 16K theoretical max IOPS is allocated.

      • For Ampere A1 shape, a minimum of 16K and a maximum of 640K theoretical max IOPS is allocated.
      • For AMD E4 and E5 shapes, a minimum of 16K and a maximum of 640K theoretical max IOPS is allocated.
      • For Intel X9 shape, a minimum of 16K to a maximum of 512K theoretical max IOPS is allocated.
13. Click Select shape.
14. Provide the following details in the Configure the DB system section.
15. Total node count: (Read-only) The number of nodes that is allocated to the standby instance. The node count will be the same as the primary node count.
16. Choose a license type: The type of license you want to use for the DB system. Your choice affects metering for billing.
    • License included means the cost of this Oracle Cloud Infrastructure Database service resource will include both the Oracle Database software licenses and the service.
    • Bring Your Own License (BYOL) means you will use your organization's Oracle Database software licenses for this Oracle Cloud Infrastructure Database service resource. For more information, see Bring Your Own License.
17. Provide the following details in the Specify the network information section.
18. Virtual cloud network: The VCN in which to create the DB system. Click Change compartment to select a VCN in a different compartment.

19. Client subnet The subnet to which the DB system attaches. For both single-node and multi-node RAC DB systems, do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet causes the private interconnect to malfunction.

    Click Change compartment to select a subnet in a different compartment.

20. Network security groups: Optionally, you can specify one or more network security groups (NSGs) for your DB system. NSGs function as virtual firewalls, enabling you to apply a set of ingress and egress security rules to your DB system. A maximum of five NSGs can be specified.

    For more information, see Access and Security and Security Rules for the DB System.

    Note
    
    If you select a subnet with a security list, the security rules for the DB system will be a union of the rules in the security list and the NSGs.
    To use network security groups:

    1. Check the Use network security groups to control traffic check box. Note that you must have a virtual cloud network selected to be able to assign NSGs to your DB system.
    2. Specify the NSG to use with the DB system. You may need to use more than one NSG. If you're not sure, contact your network administrator.
    3. To use additional NSGs, click + Another network security group.

    To provide your resources with additional security, you can use Oracle Cloud Infrastructure Zero Trust Packet Routing to ensure that only resources identified with security attributes have network permissions to access your resources. Oracle provides Database policy templates that you can use to assist you with creating policies for common database security use cases. To configure it now, you must already have created security attributes with Oracle Cloud Infrastructure Zero Trust Packet Routing. Click Show Advanced Options at the end of this procedure.

    Be aware that when you provide security attributes, as soon as it is applied, all resources require a Zero Trust Packet policy to access the cluster. If there is a security attribute on an endpoint, then it must satisfy both network security group (NSG) and Oracle Cloud Infrastructure Zero Trust Packet Routing policy (OCI ZPR) rules.

21. Host name prefix: Your choice of host name prefix for the DB system. The host name must begin with an alphabetic character, and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed is 16.
    Note
    
    The host name must be unique within the subnet. If it is not unique, the DB system will fail to provision.
22. Host domain name: The domain name for the DB system. If the selected subnet uses the Oracle-provided Internet and VCN Resolver for DNS name resolution, then this field displays the domain name for the subnet and it can't be changed. Otherwise, you can provide your choice of a domain name. Hyphens (-) are not permitted.
23. Host and domain URL: Combines the host and domain names to display the fully qualified domain name (FQDN) for the database. The maximum length is 64 characters.
24. Private IP address: Optionally, for non-RAC DB systems, you can define the IP address of the new DB system. This is useful in development contexts where you create and delete a DB system over and over, and you need each new iteration of the DB system to use the same IP address. If you specify an IP address that is currently in use within the subnet, the provisioning operation will fail with an error message regarding the invalid IP address.
25. In the Data Guard association details section, provide the following information.
    Note
    
    You can also edit the association details after provisioning if you need to. For more information, see Edit the Oracle Data Guard Association.
26. Data Guard type: Select Active Data Guard or Data Guard. Active Data Guard provides additional features including: Real-Time Query and DML Offload, Automatic Block Repair, Standby Block Change Tracking, Far Sync, Global Data Services, and Application Continuity.
    Note
    
    The Active Data Guard requires an Oracle Active Data Guard license. For more information on Active Data Guard, see Active Data Guard. For a complete overview of both Data Guard types, see Introduction to Oracle Data Guard.
27. Protection mode: The protection mode can be Maximum Performance or Maximum Availability. For information on these options, see Oracle Data Guard Protection Modes.
28. Transport type: The redo transport type used for this Oracle Data Guard association. For information on these options, see Managing Redo Transport Services for Data Protection Modes.
    Note
    
    

    • For Oracle Database 12.1 and later, the Maximum Availability protection mode supports the ASYNC and FASTSYNC transport types. The Maximum Performance protection mode supports only the ASYNC transport type.
    • For Oracle Database 11.2, the Maximum Availability protection mode supports the SYNC transport type only, while the Max Performance mode supports the ASYNC transport type only.

29. Diagnostic collection: The diagnostics collection and notifications feature enables Oracle Cloud Operations and you to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to events to get notified about resource state changes. You can enable or disable this feature at anytime.

    By default the options are selected for enabling. However, you can select to uncheck the diagnostic collection check boxes if you do not require the diagnostic feature.

    • Enable diagnostic events: Enables and allows Oracle to collect and send fault notifications about critical, warning, and information events for you.
    • Enable incident logs and trace collection: Enables and allows Oracle to receive event notifications and collect incident logs and traces for fault diagnosis and issue resolution.
    Note
    
    

    • The Enable health monitoring diagnostics collection for Oracle Cloud operations viewing is not available for the Base Database Service.
    • You are opting-in with the understanding that the list of events and log files can change in the future. You can opt-out of this feature at any time.
30. Click Show advanced options to specify advanced options for the DB system and provide the following details.
31. Fault domain: The fault domain(s) in which the DB system resides. You can select which fault domain to use for your DB system. For multi-node RAC DB systems, you can specify which two fault domains to use. Oracle recommends that you place each node of a multi-node RAC DB system in a different fault domain. For more information about fault domains, see About Regions and Availability Domains.
32. Time zone: The default time zone for the DB system is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system. For more information, see DB System Time Zone. The following options are available:
    • UTC: configures your DB system to use coordinated universal time.
    • Browser-detected: The console displays the time zone detected by your browser for this option.
    • Select another time zone: To manually specify a time zone, first make a choice using the Region or country selector to select a geographic region, then use the Time zone selector to select your required time zone.

    Tip:

    If you want to set a time zone other than UTC or the browser-detected time zone, and if you do not see the time zone you want, try selecting "Miscellaneous" in the Region or country list.
33. Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator. For more information about tagging, see Resource Tags.
34. Click Next to advance to the Database information screen and provide the following information for the initial database.
35. In the Configure standby database section, provide the following information.

36. Database image: Optional. You can specify what Oracle Database version is used for the database. You can mix database versions on the DB system, but not editions. By default, the latest database software image as the source database is used.

    Click Change database image to choose a custom database software image that you or someone in your organization have created in your tenancy.

    Select a compartment and a database version. Then select a database image from the table of available images for the Oracle Database version you selected.

    After choosing a software image, click Select to return to the Database information Screen.

37. Database password: Enter the database administrator password of the primary database in the Database password field. Use this same database administrator password for the standby database.
38. Click Show advanced options to specify advanced options for the database.
39. In the Tags tab, you can add free-form tags or defined tags to this resource. You must have permissions to use the tag namespace for defined tags. For information about using tags to manage your OCI resources, see Resource Tags.
40. Click Enable Data Guard.

    When you create the association, the details for a database and its peer display their respective roles as Primary or Standby.