Create VM clusters

Console

1. Go to the Exadata Database Service page in the Google Cloud console.

   Go to Exadata Database Service

2. Click Exadata VM Clusters.

3. In the Exadata VM Clusters section, click Create.

4. In the Basic details section, complete the following:

   1. Select the Oracle Exadata Infrastructure instance that you want to create the VM Cluster in. To create an Exadata Infrastructure instance for your VM Cluster, see Create instances.

   2. Enter a Display name for your VM Cluster to display in the Google Cloud console. The display name must be unique within your Google Cloud project.

   3. Enter a VM Cluster ID to identify your cluster. The VM Cluster ID must be unique within your Google Cloud project and can't be changed later.

   4. Select the Oracle Grid Infrastructure version from the drop-down.

5. In the VM Cluster configuration section, complete the following:

   1. Click Change DB Servers to select the database servers you want to use for VM placement. A minimum of two database servers is required.

      Only database servers that are available in the Exadata Infrastructure can be selected. Once you select the DB servers, click Submit to save.

   2. Enter the OCPU count per VM for your cluster. OCPU count can range from 2 to 126.

   3. Enter the Memory per VM for your cluster. Memory count can range from 30GB to 1,390GB.

   4. Enter the Local storage per VM for your cluster. Local storage count can range from 60GB to 1,800GB.

6. In the Exadata storage configuration section, complete the following:

   1. Enter the Usable Exadata Storage for your cluster. This can range from 2TB to 100TB and must be specified in multiples of 1TB.

   2. Check the box for Allocate storage for sparse snapshots to allow storage to be utilized for sparse snapshots. This setting can't be changed after the VM Cluster has been created.

   3. Check the box for Allocate storage for local backups to allow your cluster storage to be used for local backups. This setting can't be changed after the VM Cluster has been created.

7. In the Networking section, define the network configuration for the VM Cluster by completing the following:

   1. In the Associated network drop-down, select the VPC network you want to use from your network project. You can only choose one network from the list.

   2. In the Client IP Range field, enter the private IPv4 address range that you want to use for your VM Clusters or databases. IPv6 addresses aren't supported.

      Address ranges must use a valid CIDR notation (for example, 10.10.10.0/24). For more information on how to select client IP ranges, see Requirements for IP Address space.

   3. In the Backup IP Range field, enter the private IPv4 address range that will be used for the backup subnet. Your backup IP range can't overlap with your Client IP range. IPv6 addresses aren't supported.

      Address ranges must use a valid CIDR notation (for example, 10.10.11.0/24). For more information on how to select client IP ranges, see Requirements for IP Address space.

   4. In the Hostname prefix, specify a prefix you want to use to generate hostnames for the VM Cluster virtual machines. This prefix can only contain letters, numbers, or hyphens, and must start with a letter. The maximum allowed length is 12 characters.

8. In the SSH keys section, add the public SSH keys you'd like to use for the cluster. To add a key, enter the SSH key name in the SSH Key 1 field. For each additional key, click ADD ITEM.

   For more information on how to generate SSH keys, see Generate SSH keys.

9. In the License type section, select the type of Oracle license you're using for your cluster. Select one of the following:

   1. License included if you're creating a new license purchased as part of the Google Cloud marketplace order.

   2. Bring your own license (BYOL) if you're be using an existing Oracle license.

10. In the Diagnostics collection section, complete the following to configure monitoring for your VM Cluster:

    1. Select the Enable diagnostic events checkbox to track all cluster diagnostic events.

    2. Select the Enable health monitoring checkbox to use the monitoring console to monitor cluster health metrics.

    3. Select the Enable incident logs and trace collection checkbox to enable incident logging for your cluster.

11. In the Advanced fields section, complete the following:

    1. From the Timezone drop-down, select the timezone you'd like to use for diagnostic collection. This timezone is used for event timestamps.

    2. In the SCAN Listener Port (TCP/IP) field, enter a value to assign a SCAN listener port to your cluster. The port value can range from 1,024 to 8,000, and the default value is 1,521.

12. Click Create to create the VM Cluster.

gcloud

Use the gcloud oracle-database cloud-vm-clusters create command to create a cluster using gcloud CLI.

gcloud oracle-database cloud-vm-clusters create CLUSTER_ID
--exadata-infrastructure=EXADATA_INSTANCE_ID
--project=PROJECT_NAME
--location=REGION_ID
--display-name="DISPLAY_NAME"
--network=NETWORK_NAME
--cidr=CLIENT_SUBNET_RANGE
--backup-subnet-cidr=BACKUP_SUBNET_RANGE
--properties-license-type=LICENSE_TYPE
--properties-ssh-public-keys="SSH_KEYS"
--properties-gi-version=GI_VERSION
--properties-hostname-prefix=HOSTNAME_PREFIX_NAME
--properties-cpu-core-count=CPU_CORE_COUNT

Replace the following:

• CLUSTER_ID: a permanent identifier for your instance. The cluster ID can't be changed once set.

• EXADATA_INFRASTRUCTURE_NAME: the name of the Exadata Infrastructure instance where you'd like to create your cluster in the following format:

  projects/PROJECT_ID/locations/REGION_ID/cloudExadataInfrastuctures/EXADATA_INSTANCE_NAME
  

• PROJECT_NAME: the name of your Google Cloud project.

• REGION_ID: the region for your cluster. The region is permanent and can't be changed later. The region must match the region used to create the Exadata Infrastructure instance. For a list of available regions, see Available configurations.

• DISPLAY_NAME: a name to identify your cluster and is displayed in the Google Cloud console. The name must be unique within your Google Cloud project.

• NETWORK_NAME: the name of the network from your network VPC project that you'd like to use for your cluster in the following format:

  projects/PROJECT_ID/locations/global/NETWORK_NAME
  

  To create a VPC network project, see Configure VPC network.

• CLIENT_SUBNET_RANGE: the IPv4 address or address range that can access your cluster. Address ranges must use a valid CIDR notation (for example, 10.10.10.0/24). For more information on how to select client IP ranges, see Requirements for IP Address space.

• BACKUP_SUBNET_RANGE: the IPv4 address or address range that serves as backup to access your cluster. Address ranges must use a valid CIDR notation (for example, 10.10.10.0/24). For more information on how to select client IP ranges, see Requirements for IP Address space.

• LICENSE_TYPE: the license type associated with your Oracle Database@Google Cloud order. Only accepted values are bring-your-own-license or license-included.

• SSH_KEYS: the public SSH keys you want stored with your cluster. You can enter a single value for a single key, or an array of values for multiple keys.

• GI_VERSION: the grid infrastructure version for your cluster. To get a list of all available grid infrastructure versions, run the following command in gcloud CLI:

  gcloud oracle-database gi-versions list --location=REGION_ID
  

  Replace the following:

  • REGION_ID: the region where you're creating your cluster. For a list of available regions, see Available configurations.

• HOSTNAME_PREFIX_NAME: the prefix you want to use to generate hostnames for the VM Cluster. This prefix can only contain letters, numbers, or hyphens, and must start with a letter. The maximum allowed length is 12 characters.

• CPU_CORE_COUNT: the number of enabled CPU cores you want for your cluster.