Oracle Cloud Infrastructure Documentation

Provisioning an Exascale VM Cluster for Azure

Oracle Database@Azure enables you to provision an Oracle Exadata Database Service on Exascale Infrastructure. Learn how to provision an Exascale VM Cluster from the OracleDB@Azure blade.

Note

There are prerequisites that must be completed before you can provision Exadata Services. You need to complete the following:
  • An existing Azure subscription.
  • Purchase OracleDB@Azure in the Azure portal.
  • Select your Oracle Cloud Infrastructure (OCI).

For more information, see Onboarding with Oracle Database@Azure.

Note

The Private offer and Pay As You Go Offer purchase options have different default limits. To increase your service limit, see Requesting a Limit Increase for Database Resources.
Note

To ensure you have all the information needed for a successful provisioning flow, see the Troubleshooting and Known Issues for Exadata Services.
  1. From the Microsoft Azure portal, select OracleDB@Azure application.
  2. From the left menu, select Oracle Exadata Database Service on Exascale Infrastructure.
  3. To begin the provisioning flow, select Vm clusters, and then + Create icon.
  4. From the Basics tab of the Oracle Exadata Database Service on Exascale Infrastructure flow, enter the following information to create a Oracle Exascale VM Cluster resource.
    1. Select the Microsoft Azure subscription to which the Oracle Exascale Infrastructure will be provisioned and billed.
    2. For resource group, you can select an existing Resource group or click the Create new link to create a new resource group. If you select the Create new option, enter Name, and then click the OK button.
    3. Enter a unique Name for your Oracle Exadata VM Cluster on this subscription.
    4. Select the Region where this Oracle Exascale Infrastructure will be provisioned.
      The regions where OracleDB@Azure service is available are limited.
    5. Select an availability zone where this Oracle Exascale Infrastructure will be provisioned.
      The availability zone where OracleDB@Azure service is available are limited.
    6. Enter a Cluster name for your Exascale VM Cluster.
    7. You can choose your License type from the dropdown list.
      The License type list provides License included, and Bring your own license (BYOL) options.
    8. Select the Time zone.
      The default time zone is UTC. If you choose the Select another time option, select your Region or country. Based on your Region or country selection, Selected time zone will be populated with available options.
    9. From the dropdown list, select Oracle grid infrastructure release that you want to use for this provisioning flow.
    10. Select your Oracle grid infrastructure version from the dropdown list.
      The Grid Infrastructure Version limits the Oracle Database versions that the VM Cluster supports.
    11. Exascale Database Storage Vault has two options. You can choose the Create a new vault option or Select existing vault option.
      If you want to use your existing vault for your Exascale Database Storage Vault, chose the Database storage vault from the dropdown list.
    12. Enter a Vault name for your Exascale Database Storage Vault.
    13. To add smart flash and memory cache options, click on the checkbox.
    14. The SSH public key source allows you to select Generate new key pair, Use existing key stored in Azure, or Use existing public key.
      If you select Generate new key pair, you must enter a Key pair name for your SSH public key. If you select Use existing key stored in Azure, you must select Stored keys from the dropdown list. If you select Use existing public key you must create and use an SSH public-private key pair. For more information, see https://learn.microsoft.com/en-us/azure/virtual-machines/linux/mac-create-ssh-keys
    15. Select Next to continue.
  5. From the Configuration tab of the Oracle Exadata Database Service on Exascale Infrastructure flow, enter the following information.
    1. Specify the Number of VMs in the Cluster located under the VM Cluster allocation section.
      The maximum limit for the Number of VMs in the Cluster is 2.
    2. Specify your ECPUs enabled per VM.
      The maximum limit for ECPUs enabled per VM is 200. Your input must be multiple of 4.
    3. The default Total ECPUs enabled across VM Cluster is 16. If you want to Add reserve additional ECPU, click on the checkbox.
      If you select the Additional ECPUs, you must enter ECPUs additional reserved per VM, Total additional ECPUs reserved across VM Cluster, Total ECPU per VM, and Total ECPUs across VM Cluster. The Total ECPU per VM range is from 8 to 200.
    4. Specify the Memory per VM (GB) to allocate to each VM Cluster.
    5. Enter the Total memory across VM Cluster(GB).
    6. The File system storage capacity for Databases(GB) selector can be used to select a range from 280 (GB) to 1100 (GB).
    7. Based on your File system storage capacity for Databases(GB) selection, the Total file system storage capacity across VM Cluster will be populated with values.
    8. Select Next to continue.
  6. From the Networking tab of the Oracle Exadata Database Service on Exascale Infrastructure flow, enter the following information.
    1. The Virtual Network list allows you to select virtual network within the subscription and resource group that you have selected in the Basics section of the provisioning flow.
    2. The Client subnet list allows you to select delegated subnets that are contained within the virtual network that you have selected previously.
    3. The Backup subnet CIDR field is an optional field. It allows you to enter the CIDR for the backup subnet of your VM Cluster.
    4. Enter the Host name prefix. The prefix forms the first portion of the Exadata VM Cluster host name.
    5. The Host domain name and Host and domain URL are read-only fields and will be populated with values.
    6. The SCAN Listener Port ( TCP/IP) default is 1521. If you do not change this value, the Oracle Exadata VM Cluster is created with the default port.
    7. If you want to Add additional network igress rules, click on the checkbox.
    8. Select Next to continue.
  7. The Diagnostics Collection tab of the Oracle Exadata Database Service on Exascale Infrastructure flow allow you to specify the diagnostic events, health monitoring, and incident logs and tracing that Oracle can use to identify, track, and resolve issues. If you want to enable them, click the checkbox for each of them, and then select Next to continue.
  8. You must agree to the terms of the service, privacy policy, and agree to access permissions from the Consent tab of Oracle Exadata Database Service on Exascale Infrastructure flow.
  9. From the Tags tab of the Oracle Exadata Database Service on Exascale Infrastructure flow, you can define Microsoft Azure tags. Select Next to continue.
  10. From the Review + create tab of the Oracle Exadata Database Service on Exascale Infrastructure flow, you can check the values that you entered from the previous steps. If the validation fails, you must correct any errors before you can start the provisioning process.
  11. Select the Create button to start the provisioning flow.
  12. Select the Download + create button to download the keys and create the resource.
  13. You can monitor and manage the Status of the Deployment details from Oracle Exascale VM Cluster blade.