Exadata VM Cluster

1. To perform a management operation, in the OCI Console for the selected Exadata VM Cluster, select the Actions button, and then select the operation from the list.

   

2. To add SSH keys in the OCI Console for the selected Exadata VM Cluster, select the Add SSH keys option from the Actions dropdown list.

   1. Generate SSH key pair: Select this option to generate a new SSH key pair.

   2. Upload SSH key files: Select this option to upload existing SSH public key files. To provide multiple keys, upload multiple key files.

   3. Paste SSH keys: Select this option to paste existing SSH public keys.

   4. Select the Save button to save your changes.

   

3. To update license type in the OCI Console for the selected Exadata VM Cluster, select the Update license type option from the Actions dropdown list.

   1. The License type is either License included or Bring your own license (BYOL). Your selection will affect your billing.

   2. Select the Save button to save your changes.

   

4. To change the I/O resource management, in the OCI Console for the selected Exadata VM Cluster, select the Actions button, and the Enable IORM option from the menu. From the Enable I/O Resource Management page, you can change the following options.

   Note
   
   Note: The Enable I/O Resource Management screen allows administrators to control how Exadata VM Cluster storage I/O resources are allocated across multiple databases. This ensures fair resource usage, prevents one database from monopolizing I/O, and aligns system performance with workload priorities. IORM does not set hard limits, but uses relative shares to prioritize databases. If a database is idle, others can use its share.

   1. In the Objective radio group, select Low Latency, High Throughput, Auto, or Balanced as required. For more on each of these, select the information icon beside the value.

   2. In the Resource Plan Default Directive section, set the Share value. This value specifies the number of shares to assign to each database by default.

   3. The Percentage and Flash Cache Limit are read-only calculated fields.

   4. The Resource Plan Directives (Optional) section, allows you to add directives for individual databases to allocate a greater or lesser share of I/O resources. By default, there are no directives. Select the + Additional Directive to add one or more.

   5. If a directive is added, the Database field allows you to select an available database. The Share field allows you to increase or decrease that database’s resources. The Percentage field is calculated based on your input. The Flash Cache Limit allows you to cap this value, if available for your database.

   6. Select the Enable button to continue.

   

5. To update display name of your Exadata VM Cluster, select the Actions button, and then select Update display name option from the menu.

   1. Enter the Current display name and then enter the New display name. The display name must be 1 to 255 characters, of letters, numbers, underscores () and hyphens (-). Display name must start with a letter or underscore() and cannot contain two successive hyphens(-).

   2. Select the Update button to save your changes.

   

6. To add a tag to your Exadata VM Cluster, in the OCI Console for the selected Exadata VM Cluster, select the Actions button and the Add Tags item from the menu. From the Add Tags page, you can change following.

   1. The Namespace drop-down is a single value None (free-form tag).

   2. The Key and Value fields can be used needed.

   3. For more information on what you can do with tags, see Overview of Tagging.

   4. If you want to enter another tag, select the Add tag button.

   5. When you have added the tag(s) you want, select the Add button.

   

7. To change scaling options, in the OCI Console for the selected Exadata VM Cluster, select the Scale VM cluster button.

   1. From the Scale VM cluster page, you can scale your resource usage. The VM count shows you the current Exadata VM Cluster count.

   2. In the Resource allocation per VM section, you can modify the following values.

      1. In the OCPU count per VM field, you can enter a value. This value is constrained by your Exadata Infrastructure.

      2. The Requested OCPU count for the VM cluster is a read-only field.

      3. In the Memory per VM field, you can enter a value. This value is constrained by your Exadata Infrastructure.

      4. The Requested memory for the VM cluster (GB) is a read-only field.

      5. The VM file system storage capacity per VM (GB): Review the value, and to modify it select the Change file system configuration button.

      6. The Total VM file system storage capacity across VM Cluster (GB) field is read-only.

   3. In the Exadata storage section, you can modify the following values.

      1. In the Specify the usable Exadata storage (TB) field, you can enter a value. The prompt shows you the range of valid values. This value is constrained by your Exadata Infrastructure.

      2. In the Storage allocation section, configure the storage allocation settings for the Exadata VM cluster:

         1. Allocate Oracle chosen default storage sizes: Select this option to allocate Oracle-defined default storage sizes to the DATA, RECO, and SPARSE ASM disk groups.

         2. Allocate custom storage sizes: Select this option to specify custom storage sizes for the DATA, RECO, and SPARSE ASM disk groups within the system-defined ranges. These values override the Oracle-defined default storage sizes.

         3. Allocate storage for Exadata sparse snapshots: Enable this option if you want to create a sparse disk group required to support Exadata snapshot functionality.

         4. Allocate storage for local backups: Enable this option to allocate additional storage to the RECO disk group for backups. This option must be enabled to use local Exadata storage as a backup destination for databases created in the VM cluster.

         5. Usable storage allocation: Review the storage allocation distribution across the DATA, RECO, and SPARSE ASM disk groups. The Usable storage allocation: is a read-only calculated field.

   4. Select the Scale button when finished.

   

   

There is currently no content for this page. Oracle AI Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle AI Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

There is currently no content for this page. Oracle AI Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle AI Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

You can modify an Exadata VM Cluster in Google Cloud using OCI Terraform provider.

Prerequisites

• Terraform or OpenTofu installed

• OCI credentials configured

• HashiCorp OCI provider version >= 7.0

• Exadata VM Cluster is created using Terraform

To modify an Exadata VM Cluster, perform the following steps:

1. Create a Modify configuration file and add the import block with the Exadata VM Cluster id. The id value can be found at the Create Exadata VM Cluster output block.

   Sample Terraform Configuration using OCI Terraform Provider

   # Set OCI Provider source and version
   terraform {
     required_providers {
       # OCI Provider
       oci = {
         source = "oracle/oci"
         version = "7.29.0"
       }
     }
   }
   
   # Configure the OCI Provider
   provider "oci" {
     tenancy_ocid = "ocid1.tenancy.oc1..aaaaaaaa2pg53mzroh6r2ub72r5mxxxxxxxxxxxxxpylciiqdihofe3dq"
     user_ocid = "ocid1.user.oc1..aaaaaaaaa6wyl3kzbgogsqpsixxxxxxxxxxxxxxxxuwzkemcrgue5q"
     private_key_path = "C:\OCI-Terraform\private-key.pem" # This example is for Windows OS
     fingerprint = "6c:c7:a7:60:f2:99:62:b9:8e:01:fc:e8:9b:eb:61:61"
     region = "us-desmoines-1"
   }
   
   # Import Exadata VM Cluster Configuration
   import {
       to = oci_database_cloud_vm_cluster.oci_exa_vm_cluster
       id = "ocid1.cloudvmcluster.oc1.us-desmoines-1.anrxkljrou6knayaa7xxxxxxxxxxxxunyiz4f6sdpfe5ov2tu3wvbyrq" # Replace the OCID value
   }

2. Run the following commands in the Terminal window:

   terraform init

   terraform validate

   terraform plan -generate-config-out="C:\GoogleCloud-Terraform\Working-Directory\generated_exa_vm_cluster.tf" # An example on Windows OS

3. Open the generated_exa_vm_cluster.tf file in a text editor and copy the content.

4. Append the generated_exa_vm_cluster.tf content in the Modify configuration file. Remove the import block.

5. Run the following command in the Terminal window:

   terraform import oci_database_cloud_vm_cluster.oci_exa_vm_cluster "ocid1.cloudvmcluster.oc1.us-desmoines-1.anrxkljrou6knayaa7xxxxxxxxxxxxunyiz4f6sdpfe5ov2tu3wvbyrq" # Replace the OCID value

6. Run the following command in the Terminal window to confirm the imported state file and the generated configuration file resources are in sync:

   terraform plan

7. Update the properties/values in the Modify configuration file as required.

   Note
   
   

   Note:

   Modifying the configuration of Exadata VM Cluster using OCI Terraform provider will make the Create configuration file out of sync. To avoid out of sync Force replacement / Destroy issue, add the following lifecycle block in the Create configuration file.

   lifecycle {
       ignore_changes = [
         properties[0].db_server_ocids,
         properties[0].cpu_core_count,
         properties[0].memory_size_gb,
         properties[0].db_node_storage_size_gb,
         properties[0].data_storage_size_tb,
         properties[0].local_backup_enabled,
         properties[0].sparse_diskgroup_enabled
       ]
     }

   Sample Terraform Configuration using OCI Terraform Provider

   # __generated__ by Terraform
   # Please review these resources and move them into your main configuration files.
   
   # __generated__ by Terraform from "ocid1.cloudvmcluster.oc1.us-desmoines-1.anrxkljrou6knayaa7xxxxxxxxxxxxunyiz4f6sdpfe5ov2tu3wvbyrq"
   resource "oci_database_cloud_vm_cluster" "oci_exa_vm_cluster" {
     backup_network_nsg_ids          = ["ocid1.networksecuritygroup.oc1.us-desmoines-1.aaaaaaaa5spgwe4zrtgf3dghs3xxxxxxxxxxxpxqp2ar32faknvrpojpptaxa"]
     backup_subnet_id                = "ocid1.subnet.oc1.us-desmoines-1.aaaaaaaa4vmrgp2dcluqgxxxxxxxfbiurd7ttktoa5gwxx2ka"
     cloud_exadata_infrastructure_id = "ocid1.cloudexadatainfrastructure.oc1.us-desmoines-1.anrxkljrou6knayackcbpbksxfkxxxxxxxxxxxmfgw6cdmw55ystti7a"
     cluster_name                    = "cl-u3wvbyrq"
     compartment_id                  = "ocid1.compartment.oc1..aaaaaaaaqn5kip2ivclikxxxxxxxxxxxxrhoovfswhzc5rykq3wfkrdoa"
     cpu_core_count                  = 48
     create_async                    = null
     data_storage_percentage         = 80
     data_storage_size_in_tbs        = 4
     db_node_storage_size_in_gbs     = 120
     db_servers                      = ["ocid1.dbserver.oc1.us-desmoines-1.anrxkljr6v2haxaahos55yinuxxxxxxxxqfumsycui7quarv4cjasaq", "ocid1.dbserver.oc1.us-desmoines-1.anrxkljr6v2haxaars7dueg46sm4xxxxxxxxxxxdozenln67rxv4r3wceh6b3q"]
     defined_tags = {
       "Oracle-Tags.CreatedBy" = "ocid1.multicloudlink.oc1.iad.amaaaaaaou6knayafyn3zgqe4cwafxxxxxxxxxxx6ygzgwiln3zdhyypbtq"
       "Oracle-Tags.CreatedOn" = "2026-01-02T05:25:45.792Z"
     }
     display_name                = "demo-exadata-vm-cluster-tf"
     domain                      = "mauingybxr.v6a1fdff9.oraclevcn.com"
     freeform_tags               = {}
     gi_version                  = "23.26.0.0.0"
     hostname                    = "vm-znkeq"
     is_local_backup_enabled     = false
     is_sparse_diskgroup_enabled = false
     license_model               = "BRING_YOUR_OWN_LICENSE"
     memory_size_in_gbs          = 60
     nsg_ids                     = ["ocid1.networksecuritygroup.oc1.us-desmoines-1.aaaaaaaadmguhpdoarhi7gqtltbmxxxxxxxxx4s3jebilpquzvufst2gq"]
     ocpu_count                  = 6
     scan_listener_port_tcp      = 1521
     scan_listener_port_tcp_ssl  = 2484
     security_attributes         = {}
     ssh_public_keys             = ["ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2Xwmyn1cVUhDhqyb/B0gYQwlR88gnEJOAg+bhUvGjMB0gVCxxxxxxxxxxxYGPdrrCH/dzWcfysXzSs8XZpVmv4yYhpMC4C/4hQkBjwqgsBii5tJP7EFQjb2TfQPYbTkrn4SBNZhR1lYHr543yhB1Va7tjJNZz7 first.last@email.com"]
     subnet_id                   = "ocid1.subnet.oc1.us-desmoines-1.aaaaaaaahawbny2yivfdvfxxxxxxxxxxxxxkwo6qq27i5cazf4vevnjupa"
     system_version              = "25.1.10.0.0.251020"
     tde_key_store_type          = "OCI"
     time_zone                   = "UTC"
     vm_cluster_type             = "REGULAR"
     cloud_automation_update_details {
       is_early_adoption_enabled = false
       is_freeze_period_enabled  = false
       apply_update_time_preference {
         apply_update_preferred_end_time   = "06:00"
         apply_update_preferred_start_time = "00:00"
       }
     }
     data_collection_options {
       is_diagnostics_events_enabled = true
       is_health_monitoring_enabled  = true
       is_incident_logs_enabled      = true
     }
     file_system_configuration_details {
       file_system_size_gb = 50
       mount_point         = "$GRID_HOME"
     }
     file_system_configuration_details {
       file_system_size_gb = 15
       mount_point         = "/"
     }
     file_system_configuration_details {
       file_system_size_gb = 1
       mount_point         = "/boot"
     }
     file_system_configuration_details {
       file_system_size_gb = 20
       mount_point         = "/crashfiles"
     }
     file_system_configuration_details {
       file_system_size_gb = 4
       mount_point         = "/home"
     }
     file_system_configuration_details {
       file_system_size_gb = 3
       mount_point         = "/tmp"
     }
     file_system_configuration_details {
       file_system_size_gb = 20
       mount_point         = "/u01"
     }
     file_system_configuration_details {
       file_system_size_gb = 5
       mount_point         = "/var"
     }
     file_system_configuration_details {
       file_system_size_gb = 18
       mount_point         = "/var/log"
     }
     file_system_configuration_details {
       file_system_size_gb = 3
       mount_point         = "/var/log/audit"
     }
     file_system_configuration_details {
       file_system_size_gb = 9
       mount_point         = "reserved"
     }
     file_system_configuration_details {
       file_system_size_gb = 16
       mount_point         = "swap"
     }
   }

8. Run the following command in the Terminal window:

   terraform apply