Note:

• This tutorial requires access to Oracle Cloud. To sign up for a free account, see Get started with Oracle Cloud Infrastructure Free Tier.
• It uses example values for Oracle Cloud Infrastructure credentials, tenancy, and compartments. When completing your lab, substitute these values with ones specific to your cloud environment.

Provision Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure

Introduction

Users can now provision Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure. Exascale is a multitenant, hyper-elastic intelligent data architecture that delivers all the advantages of Exadata with all the benefits of modern clouds. The Exascale intelligent storage cloud and a pool of Exascale database-optimized compute provide scalable shared resources in the cloud while still meeting even the most demanding workload requirements. You can start with a small VM cluster and small amount of storage and easily scale as needs grow. With the introduction of Exascale infrastructure, the benefits of Oracle Exadata Database Service are now available for workloads at any scale.

Objectives

• Create a VM cluster on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure.

• Create an Exascale database storage vault to be used for your database storage.

• Provision an Oracle Database 23ai container database.

Prerequisites

• An existing Microsoft Azure subscription.

• A Microsoft Azure Virtual Network (VNet) with a subnet delegated to the Oracle Database@Azure service.

• Permissions in Microsoft Azure to create resources in the region.

• Oracle Cloud Infrastructure (OCI) Service Limits approved in the region you want to provision Oracle Exadata Database Service.

Task 1: Create a VM Cluster

1. Log in to the Microsoft Azure portal, navigate to the left pane to display a list of services and click Oracle Database@Azure.

   

2. Provision the Oracle Exadata Database Service on Exascale Infrastructure resources from Oracle Database@Azure.

   Click Oracle Database@Azure drop-down menu and then Oracle Exadata Database Service on Exascale Infrastructure.

   

3. Click Vm Clusters and select + Create to begin the provisioning flow.

   

4. In the Basics section, enter the following information and click Next.

   • Project details:

     • Subscription: Select the Microsoft Azure subscription for the Exascale VM cluster.

     • Resource group: Select an existing resource group or click Create new to create and use a new resource group for this resource.

   • Exascale VM Cluster details:

     • Name: Enter the name for the Exascale VM cluster.

     • Region: Select the region where the Exascale VM cluster will be provisioned.

     • Availability zone: Select an availability zone.

     • Cluster name: Enter a cluster name.

     • License type: The type of license you want to use for the VM cluster. The license type is either License included or Bring your own license (BYOL). Your selection will affect your billing.

     • Time zone: The default time zone is UTC. There is also an option to select another time zone.

     • Oracle grid infrastructure release: Select the Oracle Grid Infrastructure release.

     • Oracle grid infrastructure version: Select the Oracle Grid Infrastructure version.

       

   • Exascale Database Storage Vault:

     • Choose: Select either Create new vault or Select existing vault. If you select an existing vault, then select the database storage vault from the drop-down menu.

     • Vault name: Enter the vault name for the new Exascale vault.

     • Storage capacity for Databases: The amount of usable disk storage capacity that will be available for storing databases that is desired. Specify the size in gigabytes (GB).

     • (Optional) Add smart flash and memory cache options: Enter the amount of smart flash cache. It is based on a percentage of storage capacity.

     • Security: The SSH public key source can be selected to Generate new key pair, Use existing key stored in Azure, or Use existing public key.

       • If you select Generate new key pair, you must give your newly generated key a unique name.
       • If you select Use existing key stored in Azure, you must select that key from a drop-down menu of defined key for your subscription.
       • If you select Use existing public key, you must provide an RSA public key in single-line format (starting with ssh-rsa) or the multi-line PEM format. You can generate SSH keys using ssh-keygen or Linux and OS X, or PuTTYGen on Windows.

       

5. In the Configuration section, enter the following information and click Next.

   • In VM Cluster allocation, select resources for the VM cluster.

     • Number of VMs in the cluster: Specify the number of the VMs that you want to configure for the cluster, between 2 and 10.
     • ECPUs enabled per VM: Specify the number of ECPU cores that you want to enable for the VM cluster. The minimum is 8 ECPU. The value you select must be a multiple of 4.

   • (Optional) Add reserve additional ECPU

     • ECPUs additional reserved per VM: (read-only) Indicates the additional reserved ECPUs.
     • Total additional ECPUs reserved across VM Cluster: (read-only).
     • Total ECPUs per VM: Enter the total number of ECPUs to allocate per VM. The total must be between 8 and 200.
     • Total ECPUs enabled across VM Cluster: (read-only).

   • Memory per VM (GB): (read-only) Displays the amount of memory allocated to each VM. Memory is calculated based on 2.75 GB per ECPU.

   • Total memory across VM cluster (GB): (read-only) The total memory across VM cluster (GB) field is automatically updated to provide you with the total amount of memory allocated across the VM cluster.

   

   • VM file system storage capacity per VM (GB): Specify storage capacity per VM in gigabytes (GB).

     Note: Enter how much storage you want for the VM filesystem. The VM filesystem storage includes /u02 capacity, where your database homes will be created, along with all the other VM file systems. The extra capacity selected beyond system minimum will expand /u02 file system.

   

6. In the Networking section, enter the following information to configure the network settings and click Next.

   • Virtual network: Select the virtual network (VNet) in which you want to create the VM cluster.

     Note: The drop-down menu will only list virtual networks that are located within the subscription and resource group that you have selected in the Basics section. If the drop-down menu is empty, you may need to specify a different subscription or resource group, or create a virtual network within the selected resource group.

   • Client subnet: Select the client subnet.

     Note: The drop-down menu will only list delegated subnets that are contained within the virtual network that you have selected above. If the drop-down menu is empty, you may need to specify a different virtual network, or create a delegated subnet within the selected virtual network.

   • Backup subnet: Leave this field blank as Oracle will automatically assign it. This is the subnet to use for the backup network, which is typically used to transport backup information to and from the backup destination, and for Oracle Data Guard replication.
   • Hostname prefix: Enter a hostname. The prefix forms the first portion of the Exadata VM cluster host name. Recommended maximum: 12 characters.
   • Host Domain Name: (read only) Displays the host domain name for the VM cluster.

   • Host and domain URL: (read only) This read-only field combines the host and domain names to display the fully qualified domain name (FQDN) for the database.

     Note: If custom DNS is selected, this field is composed of the entered hostname and selected private zone. If custom DNS is not selected, this field is composed of the entered hostname, selected subnet, and selected virtual network.

   • SCAN Listener Port (TCP/IP): Assign a SCAN listener port (TCP/IP) in the range between 1024 and 8999. The default is 1521. If you do not assign the port, then the Exadata VM cluster is created with the default port.
   • Add additional network ingress rules: Add additional network CIDR ranges (such as application or hub subnet ranges) to the Network Security Group (NSG) ingress rules for this VM cluster. The selected virtual network’s CIDR is added by default.

   

7. In the Diagnostics Collection section, select all to enable diagnostics collection and click Next.

   Diagnostic Collection: Enabling diagnostics collection and notifications allow you and OCI operations to identify, investigate, track, and resolve guest VM issues quickly and effectively.

   

8. In the Consent section, you must agree to the terms of service, privacy policy, and agree to access permissions. Select Next to continue.

   

9. In the Tags section, you can define Microsoft Azure tags and click Next.

   

10. In the Review + create section, a short validation process is run to 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. Click Create to start the provisioning flow.

    

    Go to the Oracle Exadata Database Service on Exascale Infrastructure page to monitor and manage the state of your Oracle Exadata VM cluster environments.

    Once the provisioning process of the Oracle Exascale VM Cluster is completed, the state of the VM cluster will show as Available.

    

12. Click the created VM cluster to view the details of the Oracle Exascale VM cluster.

    

    Details about the Oracle Exascale VM Cluster is displayed such as Resource Allocation, Version, State, OCI Database URL, Storage Vault and Networking.

    

    In the Oracle Exascale VM Cluster Overview section, click Storage Vault to view the details of the Exascale Database Storage Vault.

    

    Information about the Oracle Exascale DB Storage Vault is displayed such as Exascale database storage details in the Overview section.

    

Task 2: Provision a Container Database

1. Go to the Oracle Exascale VM cluster, click Overview and Go to OCI.

   

2. Log in to the OCI Console and navigate to VM Cluster Details.

   

3. Under Resources, select Container databases and click Create container database.

   

4. In the Create container database page, enter the following information.

   • Basic information for container database:

     • Provide the database name: Enter a name for the database.
     • Provide a unique name for the database (Optional): Enter a unique name for the database.
     • Select a database version: Select the database version available.
     • Provide a PDB name (Optional): Enter the name of the first PDB to be created.

     

   • Specify a database Home:

     • Database Home source: Select to use an existing Database Home or Create a new Database Home.

     • Database Home display name: Use the default database home name or enter a database home name.

     • Change Database Image (Optional): Determines what Oracle Database version is used for the database. By default, the latest Oracle-published database software image is selected. Select to use an older Oracle-published image or a custom database software image that you have created in advance.

       

   • Create administrator credentials:

     • Password: Password must be 9 to 30 characters and contain at least 2 uppercase, 2 lowercase, 2 special, and 2 numeric characters. The special characters must be \, _, #, or -.

     • Confirm Password: Enter the same password.

       

5. In the Configure Database backups page, if you accept the defaults setting, the database will be backed up using the Oracle Database Autonomous Recovery Service. You have the option to use OCI Object Storage by changing the Backup destination. The database will not be backed up if you deselect Enable automatic backups. Automatic backups can be enabled after the container database is created.

   

6. Click Show advanced options and enter the following information.

   • Management: You can add Oracle SID prefix (Optional) and select the Character set and National Character set.

   

   • Encryption: Configure key management, you have options to manage database keys. Select Use Oracle-managed keys to manage database keys using the wallet or select Use customer-managed keys to manage database keys using OCI Vaults.

     

   • Tags: Apply free-form or defined tags to this resource.

     

7. Click Create container database.

   

   Once the provisioning process of the container database is completed, the state of the container database will show as Available.

   

8. In the Container Database details page, under Resources, select Pluggable Databases.

   

   Click Pluggable Database to view the details of the pluggable database.

   

Related Links

• Get All Exadata Benefits for Less on Oracle Database@Azure

• What’s New in Oracle Database@Azure

• What’s New in Oracle Exadata Database Service on Exascale Infrastructure

• Oracle Exadata Database Service on Exascale Infrastructure Overview

• Oracle LiveLabs Workshop: Get Started with Oracle Exadata Database Service on Exascale Infrastructure

Acknowledgments

• Authors - Leo Alvarado, Tammy Bednar (Product Management)

More Learning Resources

Explore other labs on docs.oracle.com/learn or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.

For product documentation, visit Oracle Help Center.

---

Title and Copyright Information

<

Provision Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure

G29092-01

Copyright ©2025, Oracle and/or its affiliates.