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
-
Confirm you have an active marketplace order for Oracle Database@Google Cloud.
-
Enable the Oracle Database@Google Cloud API for the project.
-
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
-
Go to the Exadata Database Servicepage in the Google Cloud console.
-
In the Exadata Infrastructuresection, click Create.
-
In the Instance detailssection, complete the following:
-
Enter an Infrastructure display nameto display in the Google Cloud console. The name must be unique within your Google Cloud project.
-
Enter an Infrastructure IDto display in the Google Cloud project. This identifier is permanent.
-
Select a Regionfor your Exadata Infrastructure. The region choice is permanent and can't be changed later.
-
-
In the Machine configurationsection, complete the following:
-
Select an Exadata Infrastructure modelfor your instance. The list shows infrastructure models available based on the region you selected.
-
Select the values for the following configurations:
- Database server type(applicable only to
X11M
) - Storage server type(applicable only to
X11M
) - Database servers(minimum 2, maximum 32)
- Storage servers(minimum 3, maximum 64)
- Database server type(applicable only to
-
-
In the Maintenancesection, click Changeto open the Edit Maintenancewindow and configure your instance's maintenance settings.
-
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 actionsetting.
-
-
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 .
-
-
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 Saveto save the maintenance settings for your instance.
-
-
Click Createto 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.
C#
Go
Java
Node.js
PHP
Python
Ruby
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.