Managing Autonomous Exadata VM Clusters

An Autonomous Exadata VM Cluster is a set of symmetrical VMs across all Compute nodes.

Autonomous Container and Database run all the VMs across all nodes enabling high availability. It consumes all the resources of the underlying Exadata Infrastructure.

After you have created the Autonomous Exadata VM Cluster, you can create up to 12 Autonomous Container Database resources on it, depending on the capacity of your Exadata Infrastructure hardware, as described in Available Exadata Infrastructure Hardware Shapes.

About Autonomous Exadata VM Clusters

  • Please contact your Oracle sales representative to understand the infrastructure upgrades required for supporting Oracle Autonomous Databases.
  • Create multiple Autonomous Exadata VM Clusters on a single Exadata Infrastructure resource.
  • Create both Autonomous Exadata VM Clusters and Exadata VM Clusters on the same Exadata Infrastructure.
  • Support for multiple VM Clusters lets you:
    • Schedule separate maintenance runs for each Autonomous VM Cluster on the same Exadata Infrastructure.
    • Choose different license models for Autonomous Databases on the same Exadata Infrastructure.
    • Create and test Autonomous Data Guard between Autonomous Exadata VM Clusters on the same Exadata Infrastructure.
    • Customize compute, storage, and memory of each Autonomous Exadata VM Cluster configuration for the intended workload.

Create an Autonomous Exadata VM Cluster

Follow these steps to create an Autonomous Exadata VM cluster on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. Click Create Autonomous Exadata VM Cluster.
  4. In the Create Autonomous Exadata VM Cluster dialog, enter the following general information:
    • Compartment: Specify the compartment in which the Autonomous Exadata VM Cluster will be created.
    • Display Name: A user-friendly description or other information that helps you easily identify the infrastructure resource. The display name does not have to be unique. Avoid entering confidential information.
    • Exadata Infrastructure: Select an Exadata Infrastructure.
    • VM Cluster Network: Select a VM Cluster Network.
    • Configure Autonomous VM Cluster Resources
      Note

      The minimum and maximum values for these parameters change in relation to each other, for example, the OCPU count allocation will impact the number of ACDs customers can create.
      • Node Count: Number of database servers in the Exadata infrastructure. You cannot modify the node count.
      • Maximum number of Autonomous Container Databases for the Autonomous VM Cluster: The number of ACDs specified represents the upper limit on ACDs. These ACDs must be created separately as needed. ACD creation also requires 2 available OCPUs per node.
      • OCPU count per node: Specify the OCPU count for each individual VM. The minimum value is 5 OCPUs per VM.
      • Database memory per OCPU (GB): The memory per OCPU allocated for the Autonomous Databases in the Autonomous VM CLuster.
      • Allocate Storage for Local Backups: Check this option to configure the Exadata storage to enable local database backups.
      • Autonomous Database storage for the Autonomous VM Cluster (TB): Data storage allocated for Autonomous Database creation in the Autonomous VM Cluster.
  5. Configure automatic maintenance.
    1. Click Edit Maintenance Preferences.
      On the Edit Maintenance Preferences page do the following:
      • No preference: The system assigns a date and start time for infrastructure maintenance.
      • Specify a schedule: Choose your preferred month, week, weekday, start time, and lead time for infrastructure maintenance.
        • Under Maintenance months, specify at least one month for each quarter during which Exadata infrastructure maintenance will take place. You can select more than one month per quarter. If you specify a long lead time for advanced notification (for example, 4 weeks), you may wish to specify 2 or 3 months per quarter during which maintenance runs can occur. This will ensure that your maintenance updates are applied in a timely manner after accounting for your required lead time. Lead time is discussed in the following steps.
        • Optional. Under Week of the month, specify which week of the month maintenance will take place. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. If you do not specify a week of the month, Oracle will run the maintenance update in a week to minimize disruption.
        • Optional. Under Day of the week, specify the day of the week on which the maintenance will occur. If you do not specify a day of the week, Oracle will run the maintenance update on a weekend day to minimize disruption.
        • Optional. Under Start hour, specify the hour during which the maintenance run will begin. If you do not specify a start hour, Oracle will pick the least disruptive time to run the maintenance update.
        • Under Lead Time, specify the minimum number of weeks ahead of the maintenance event you would like to receive a notification message. Your lead time ensures that a newly released maintenance update is scheduled to account for your required minimum period of advanced notification.
    2. Click Save Changes.
  6. Choose the license type you wish to use.

    Your choice affects metering for billing. You have the following options:

    • Bring your own license: If you choose this option, make sure you have proper entitlements to use for new service instances that you create.
    • License included: With this choice, the cost of the cloud service includes a license for the Database service.
  7. The following Advanced Options are available:
    • Time zone: The default time zone for the Exadata Infrastructure is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system.
      Note

      If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another time zone option, select a Region or contry, and then select the corresponding Time zone.

      If you do not see the region or country you want, then select Miscellaneous, and then select an appropriate Time zone.

    • Listener: VM Cluster Networks are created with the default ports (non-TLS: 1521 and TLS: 2484). You can select a non-default SCAN listener port for both TLS and non-TLS connections within the permissible range of ports.
      Note

      • You can configure SCAN listener ports and TLS/mTLS authentication mode only when you provision a new VM Cluster.
      • You cannot change the settings after provisioning the VM Cluster.
      • Once configured, the configuration applies to all ACDs in the cluster.
      • Non-TLS port:
        • Default: 1521
        • Permissible range:1024 - 8999
        • Exceptions:
          • Agent port: 7070
          • Admin port: 7879
          • Connect to agent port: 7060
          • Oracle notification service: 6100, 6200
      • TLS port:
        • Default: 2484
        • Permissible range:1024 - 8999
        • Exceptions:
          • Agent port: 7070
          • Admin port: 7879
          • Connect to agent port: 7060
          • Oracle notification service: 6100, 6200
      • Enable mutual TLS (mTLS) authentication: Select or deselect this check box to choose between one-way TLS and mutual TLS for database SSL certificates.
    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
  8. Click Create Autonomous Exadata VM Cluster.

View a List of Autonomous Exadata VM Clusters

Follow these steps to view a list of autonomous Exadata VM clusters on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.

    Autonomous VM Cluster view page displays details that include total and available OCUPs, Reclaimable OCUPs, total and available storage in TB, and total and available ACDs.

View Details of an Autonomous Exadata VM Cluster

Follow these steps to view detailed information about an autonomous Exadata VM cluster on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, click the display name of the Exadata VM cluster you wish to view details.

    (or)

    1. Click Exadata Infrastructure.
    2. In the list of Exadata Infrastructure, click the display name of the Exadata Infrastructure you wish to view details.

      Infrastructure Details page is displayed.

    3. Under Resources, click Autonomous Exadata VM Clusters.
    4. In the list of Autonomous Exadata VM Clusters, click the display name of the Autonomous Exadata VM Clusters you wish to view details. Or, click the action menu (three dots), and then select View Details.

      Autonomous Exadata VM Clusters Details page is displayed.

      Autonomous VM Cluster Details page displays details that include total and available OCPUs, Reclaimable OCPUs, total and available storage in TB, and total and available ACDs.

Schedule Oracle-Managed Infrastructure Updates

Exadata Cloud Service updates are released on a quarterly basis. You can set a maintenance window to determine the time your quarterly infrastructure maintenance will begin.

You can also view scheduled maintenance runs and the maintenance history of your Autonomous Exadata VM Cluster in the Oracle Cloud Infrastructure Console.

Set the Automatic Maintenance Schedule for Autonomous Exadata VM Cluster

Learn how to set the maintenance schedule for an Autonomous Exadata VM Cluster on an Oracle Exadata Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, find the Autonomous Exadata VM Cluster you want to set the maintenance window for and click its highlighted name.
  4. On the Autonomous Exadata VM Cluster Details page, under Maintenance, click the edit link in the Maintenance Details field.
  5. In the Edit Automatic Maintenance page, select Specify a schedule.
  6. Under Maintenance months, specify at least one month for each quarter during which Autonomous Exadata VM Cluster maintenance will take place.
    You can select more than one month per quarter. If you specify a long lead time for advanced notification (for example, 4 weeks), you may wish to specify 2 or 3 months per quarter during which maintenance runs can occur. This will ensure that your maintenance updates are applied in a timely manner after accounting for your required lead time. Lead time is discussed in the following steps.
  7. Optional. Under Week of the month, specify which week of the month maintenance will take place.
    Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. If you do not specify a week of the month, Oracle will run the maintenance update in a week to minimize disruption.
  8. Optional. Under Day of the week, specify the day of the week on which the maintenance will occur.
    If you do not specify a day of the week, Oracle will run the maintenance update on a weekend day to minimize disruption.
  9. Optional. Under Start hour, specify the hour during which the maintenance run will begin. If you do not specify a start hour, Oracle will pick the least disruptive time to run the maintenance update.
  10. Under Lead Time, specify the minimum number of weeks ahead of the maintenance event you would like to receive a notification message.
    Your lead time ensures that a newly released maintenance update is scheduled to account for your required minimum period of advanced notification.
  11. Click Save Changes.

View or Edit the Time of the Next Scheduled Maintenance for Autonomous Exadata VM Cluster

Learn how to view and edit the time of the next scheduled maintenance.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, find the Autonomous Exadata VM Cluster you want to set the maintenance window for and click its highlighted name.
  4. On the Autonomous Exadata VM Cluster details page, under Maintenance, click the view link in the Next Maintenance field.
  5. On the Maintenance page, scheduled maintenance events are listed.
  6. Optional. To change the time of the next scheduled maintenance, click the Edit link in the Scheduled Start Time field.
  7. In the Edit Infrastructure Maintenance Scheduled Start Time page, enter a date and time in the Scheduled Start time field.
    The following restrictions apply:
    • You can reschedule the infrastructure maintenance to a date no more than 180 days from the prior infrastructure maintenance. If a new maintenance release is announced prior to your rescheduled maintenance run, the newer release will be applied on your specified date. You can reschedule your maintenance to take place earlier than it is currently scheduled. You cannot reschedule the maintenance if the current time is within 2 hours of the scheduled maintenance start time.
    • Oracle reserves certain dates each quarter for internal maintenance operations, and you cannot schedule your maintenance on these dates.

View the Maintenance History of Autonomous Exadata VM Cluster

Learn how to view the maintenance history for an Autonomous Exadata VM Cluster.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, find the Autonomous Exadata VM Cluster you want to set the maintenance window for and click its highlighted name.
  4. On the Autonomous Exadata VM Cluster details page, under Maintenance, click the view link in the Next Maintenance field.
  5. Click Maintenance History to see a list of past maintenance events including details on their completion state.

Change the License Type on an Autonomous VM Cluster

Follow these steps to update the license type of an autonomous Exadata VM cluster on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, click the display name of the Exadata VM cluster you wish to administer.
  4. Click Update License Type.
  5. On the Update License Type dialog box, choose one of the following license types.
    • Bring Your Own License (BYOL): Select this option if your organization already owns Oracle Database software licenses that you want to use on the VM cluster.
    • License Included: Select this option to subscribe to Oracle Database software licenses as part of Exadata Database Service on Cloud@Customer.

    Updating the license type does interrupt the operation of the VM cluster.

  6. Click Save Changes.

Move an Autonomous Exadata VM Cluster to Another Compartment

Follow these steps to move an autonomous Exadata VM cluster on an Oracle Exadata Database Service on Cloud@Customer system from one compartment to another compartment.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Exadata VM Clusters.
  3. In the list of Autonomous Exadata VM Clusters, click the display name of the Exadata VM cluster you wish to administer.
  4. Click Move Resource.
  5. Select the new compartment.
  6. Click Move Resource.

Terminate an Autonomous Exadata VM Cluster

Follow these steps to terminate an autonomous Exadata VM cluster on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. In the list of Autonomous Exadata VM Clusters, click the display name of the Exadata VM cluster you wish to administer.
  3. Click Terminate.
  4. Confirm that you wish to terminate your Autonomous Exadata VM Cluster in the confirmation dialog.
  5. Click Terminate VM Cluster.

Using the API to Manage Autonomous Exadata VM Clusters

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

The following table lists the REST API endpoints to manage Autonomous Exadata VM Clusters.

Operation REST API Endpoint

Create an Autonomous Exadata VM Cluster

CreateAutonomousVmCluster

View a list of Autonomous Exadata VM Clusters

ListAutonomousVmClusters

View details of an Autonomous Exadata VM Cluster

GetAutonomousVmCluster

Change the license type of an Autonomous VM Cluster

UpdateAutonomousVmCluster

Move an Autonomous Exadata VM Cluster to another compartment

ChangeAutonomousVmClusterCompartment

Terminate an Autonomous Exadata VM Cluster

DeleteAutonomousVmCluster