Provisioning Oracle Exadata Infrastructure is a time-consuming process. Provisioning an Oracle Exadata Infrastructure is a prerequisite for provisioning Oracle Exadata VM Clusters and any Oracle Exadata Databases.

1. From Google Cloud console, open the Oracle Database@Google Cloud application.
2. From the left menu, select the Exadata Database menu item.
3. By default, the Oracle Exadata Infrastructure tab is selected. To create a Oracle Exadata VM Cluster resource, select that tab first.
4. Select the + CREATE icon.
5. In the Instance details section, enter the following information.
   1. Enter an Infrastructure display name. It is required, and must be unique to your account.
   2. Enter an Infrastructure ID. It is required, and must be unique to your account. It can be the same value as the Infrastructure display name.
   3. Select the Region from the drop-down list of available regions. This field is required, and cannot be changed after provisioning.
   4. The Oracle Cloud Account is a read-only field, and should be the value for your Oracle Cloud Infrastructure (OCI).
6. In the Machine configuration section, enter the following information.
   1. Select the Exadata infrastructure model from the available configurations. This selections on this list are limited to those supported by Oracle Database@Google Cloud in the selected region. For more information on the models, see Oracle Exadata Infrastructure Models.
   2. Enter the number of Database servers, in the range from 2 to 32. If you change the value of Database servers, the read-only OCPUs field recalculates.
   3. Enter the number of Storage servers, in the range from 3 to 64. If you change the value of Storage servers, the read-only Storage size field recalculates.
7. By default, the Maintenance section has default values for Maintenance Method Preference, Custom action timeout, Quarterly Maintenance Schedule, and Customer contacts. Select the CHANGE button to edit any of these values.
   1. The Maintenance method is selectable as either Rolling or Non-rolling. This value determines the update sequence to either eliminate downtime or minimize downtime.
   2. The Enable custom actions before performing maintenance of DB servers checkbox enables you to indicate that there are maintenance actions you will perform outside of Oracle's purview. For Rolling maintenance, this checkbox forces maintenance runs to wait for a custom action with a configured timeout before maintenance can start on each database server. For Non-rolling maintenance, this checkbox forces maintenance runs to wait for a custom action with a configured timeout before maintenance across all database servers.
   3. The Maintenance schedule is selectable as either No preference or Specify a schedule.
   4. If you select Specify a schedule for your Maintenance schedule, you must at least one month, but you can set two or three months, within each quarter, Quarter 1, Quarter 2, Quarter 3, and Quarter 4. You must at least one week, but you can set two, three, or four months, within each month for the Week of the month field. You must at least one day, but you can set any combination up to all seven days, within each week for the Day of the week field. You must at least one four-hour block, but you can set any combination of the available four-hour blocks, within each day for the Hour of the day field. Notification lead time is selectable as 1, 2, 3, or 4 weeks in advance.
   5. The Maintenance contacts allows you to enter up to 10 unique email addresses to be contacted for maintenance notifications. You can also delete an existing Maintenance contact.
   6. When you have made the changes you want, select the SAVE button to save your modifications, or the CLOSE button to return without saving the modifications.
8. You are now ready to provision your Oracle Exadata Infrastructure. Select the CREATE button to begin the provisioning process, or the CANCEL button to stop the process without provisioning.
9. Wait for the Oracle Exadata Infrastructure provisioning process to complete before attempting to provision any Oracle Exadata VM Clusters on that Oracle Exadata Infrastructure.