User Managed Data Distribution with Data Guard Replication

When you select User managed data distribution with Data Guard replication, continue the configuration of the following options:

Number of data spaces: Select the number of data spaces you need for your User managed data distribution topology.

Map and table views

Use the Show map toggle to select between the map and list view to configure the nodes.

• Map view: The map view filters and shows you the available Exadata clusters where nodes can be deployed. To configure nodes using the map, select an available region, select Configure nodes.

• Table view: With Show map switched off you can configure the nodes in a tabular format. To configure each node, select Edit in the Actions menu (three dots).

Data space options

Whether in Map or Table view, you configure the following options for the data spaces.

• Region: Select the OCI region where you would like to host your data space.

• Data space: Enter the name of the data space.

• Replica: Enter a name for the logical unit that will contain the primary nodes in this data space. When Data Guard standby nodes are added to the deployment, you will configure another Replica for them.

• VM cluster: Select a cluster available in the selected region.

  Note: It is recommended that you use one VM cluster per node.

• ECPU count: Enter the number of ECPU cores to enable for each node. Specify the number of ECPUs as an integer. Available cores are subject to your tenancy’s service limits.

  You must enter a minimum of 16 ECPUs per node.

  ECPUs are based on the number of cores, elastically allocated, from the shared pool of Exadata database servers and storage servers. Aggregated ECPU consumption on a given cluster is 1.5 times the ECPU count.

  Note that a number of ECPUs are consumed in overhead and are not available to the nodes.

  See Oracle Cloud Infrastructure Documentation for more information.

• Auto scaling: Enable automatic scaling based on workload per node. This value is passed on to the Autonomous AI Database so that it can manage ECPU auto scaling.

  See Enable or Disable Auto Scaling of an Autonomous AI Database on Dedicated Exadata Infrastructure for details.

• Storage: GB of storage to allocate to the node (database)

With nodes configured you can return to Catalog configuration.