Create Exadata Infrastructure instances

This page describes how to create an Exadata Infrastructure instance in Google Cloud.

In Oracle Database@Google Cloud, you can create an Exadata Infrastructure instance in Google Cloud using Google Cloud console or the Oracle Database@Google Cloud API. You need to create an instance before you can create a VM Cluster.

To learn more about Oracle Database@Google Cloud, see Product overview. For a list of available regions where you can create an instance, see Available configurations.

Before you begin

• Set up gcloud CLI and enable the API.

• Confirm you have an active marketplace order for Oracle Database@Google Cloud.

• Enable the Oracle Database@Google Cloud API for the project.

  Enable the Oracle Database@Google Cloud API

• Confirm that you have the required roles necessary to create an instance: cloudExadataInfrastructureAdmin.

  For more information on how to assign roles, see Apply IAM roles.

Create an Exadata Infrastructure instance

The following section covers how to create an instance in Google Cloud using the Google Cloud console or Google Cloud CLI.

Console

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

   Go to Exadata Database Service

2. In the Exadata Infrastructure section, click Create.

3. In the Instance details section, complete the following:

   1. Enter an Infrastructure display name to display in the Google Cloud console. The name must be unique within your Google Cloud project.

   2. Enter an Infrastructure ID to display in the Google Cloud project. This identifier is permanent.

   3. Select a Region for your Exadata Infrastructure from the drop-down. The region choice is permanent and can't be changed later.

4. In the Machine configuration section, complete the following:

   1. Select an Exadata Infrastructure model for your instance using the drop-down.

   2. Enter the Database servers for your instance. Database servers can range from 2 to 32.

   3. Enter the Storage servers for your instance. Storage servers can range from 3 to 64.

5. In the Maintenance section, click Change to open the Edit Maintenance window and configure your instance's maintenance settings.

   1. Under Maintenance method, click one of the following:

      • Rolling: the system updates the servers one at a time with no downtime.

      • Non-rolling: the system shuts down and updates the servers in parallel. This method minimizes maintenance time, but incurs a full system shutdown.

      If you want to perform custom actions outside of Oracle's purview before starting maintenance on your servers, select the checkbox for the Enable custom action setting.

   2. Under Maintenance schedule, select one of the following:

      • No preference: the system assigns a date and start time for your instance maintenance.

      • Specify a schedule: choose your preferred month, week, weekday, and start time for the instance's maintenance.

      To learn more about how maintenance works for Exadata Infrastructure resources, see Oracle-managed Exadata Cloud Infrastructure Maintenance.

   3. Under Maintenance contacts, you can add up to 10 unique maintenance contacts. To add a contact, click Add contact, enter the email address of the contact, and then click Add.

      Contacts must be added one at a time.

   Once you have completed all maintenance fields, click Save to save the maintenance settings for your instance.

6. Click Create to create the instance.

gcloud

Use the gcloud oracle-database cloud-exadata-infrastructures create command to create an instance using gcloud CLI.

gcloud oracle-database cloud-exadata-infrastructures create INSTANCE_ID
--location=REGION_ID
--display-name=DISPLAY_NAME
--properties-shape="Exadata.X9M"
--properties-compute-count=COMPUTE_COUNT
--properties-storage-count=STORAGE_COUNT

Replace the following:

• INSTANCE_ID: a permanent identifier for your instance. The instance ID can't be changed once set.
• REGION_ID: the region for your instance. The region is permanent and can't be changed later. For a list of available regions, see Available configurations.
• DISPLAY_NAME: a name to identify your instance and is displayed Google Cloud console. The name must be unique within your Google Cloud project.
• COMPUTE_COUNT: the compute capacity is the number of database servers for your instance and can range from 2 to 32.
• STORAGE_COUNT: the storage capacity for your instance and can range from 3 to 64.

What's next

• Learn how to manage or delete an instance.
• Create a VM Cluster for your Exadata Infrastructure instance.
• Configure Identity and Access Management roles for an instance.
• Use monitoring metrics to monitor your instances.