Configure Exadata Database Service for Developers on Oracle Exadata Database Service on Dedicated Infrastructure and Oracle Exadata Database Service on Cloud@Customer

Introduction

Users can now configure Exadata Database Service for Developers on Exadata Database Service on Dedicated Infrastructure and Exadata Database Service on Cloud@Customer. This feature will allow users to develop applications on Exadata Database Service using a no-cost Oracle Database license. Users can provision a new Exadata Database-Developer type of VM Cluster to run Exadata Database Service and will only pay for the cost of the infrastructure. If using the previously idle capacity of an existing Exadata Cloud Infrastructure, users will be able to develop in an Exadata Database–Developer VM cluster for no additional cost.

The Exadata Database–Developer VM Cluster type is intended for developing applications only and is subject to limitations to prevent running production workloads in a developer VM Cluster. Limits will be placed on the number of threads per PDB, the amount of memory per PDB, the size of the database per PDB, and the number of sessions per PDB. Advanced database features like RAC and Data Guard will not be available.

Unlike other free alternatives targeted at developers that provide no support, Exadata Database Service for Developers provides assistance from Oracle Support with SRs filed as Technical Issue or General Guidance.

Objectives

Prerequisites

Task 1: Create an Exadata Database-Developer VM Cluster on Oracle Exadata Database Service on Dedicated Infrastructure

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Dedicated Infrastructure.

    Description of the illustration navigate-oci-console.png

  2. In the Exadata VM clusters page, Click Create Exadata VM Cluster.

    Description of the illustration create-exadata-vmclusters.png

  3. On the Create Exadata VM Cluster window, provide the following:

    • Provide the display name: Enter the name for the VM Cluster.
    • Select a compartment: Select a compartment where you want the VM Cluster to be created.
    • Select the Exadata Infrastructure: Choose the Exadata Infrastructure to host the VM Cluster

  4. For the VM Cluster Type, choose Exadata Database-Developer

    Description of the illustration select-exadata-database-developer.png

  5. Complete the rest of the required fields in the Create Exadata VM Cluster page as you would for any other cluster.

    You are limited to a single VM in the cluster, and only the License Included license type is available. When finished, click Create.

    Description of the illustration create-vm-cluster.png

    The VM Cluster Details page is now displayed. While the creation process is running, the lifecycle state of the VM cluster shows Provisioning.

    Description of the illustration create-vm-cluster-provisioning.png

    When the VM cluster creation process completes, the state of the VM cluster changes to Available.

    Description of the illustration create-vm-cluster-available.png

    The General information section on the VM Cluster information shows the VM type configured, which, in this case, is Exadata Database-Developer.

    Note: The resulting VM Cluster will behave the same as any other VM Cluster. You can create one or more CDBs, with any number of cores, memory, or storage. Each CDB can have one or more PDBs. The database will detect it is running in a Developer VM Cluster and limit the resources available to any one PDB as described below:

    • Max 2 threads per PDB (enforced by the database).
    • Max 8GB memory per PDB (enforced by the database).
    • Max 20GB database size per PDB (enforced by the database).
    • Max 30 sessions per PDB (enforced by the database).
    • CDB/PDB only, no 19c non CDB databases.
    • Single-instance only (enforced by cloud automation).
    • No automation to create Data Guard Association (enforced by cloud automation).
    • Manual Data Guard setup not allowed by policy.
    • Backup to same backup destinations as standard service. No cross region backup/restore (enforced by cloud automation).
    • Minimum RU 19.26 (Jan 2025) or 23.6 (Oct 2024).
    • You cannot switch the VM Cluster Type Exadata Database-Developer to another VM Cluster type (enforced by cloud automation).
    • License type must be license included–BYOL is not allowed

Acknowledgments

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.