Manage VM Clusters

Learn how to manage your VM clusters on Exadata Cloud Infrastructure.

Introduction to Scale Up or Scale Down Operations

With the Multiple VMs per Exadata system (MultiVM) feature release, you can scale up or scale down your VM cluster resources.

Scale VM Resources in Multi VM Enabled Infrastructure

Increase or decrease the OCPUs, memory, storage or local disk size (/u02) storage available to a VM cluster

Note

Oracle doesn't stop billing when a VM or VM Cluster is stopped. To stop billing for a VM Cluster, lower the OCPU count to zero.

Scaling up or down of these resources requires thorough auditing of existing usage and capacity management by the customer DB administrator. Review the existing usage to avoid failures during or after a scale down operation. While scaling up, consider how much of these resources are left for the next VM cluster you are planning to create. Oracle Exadata Database Service on Dedicated Infrastructure tooling calculates the current usage of memory, local disk, and ASM storage in the VM cluster, adds headroom to it, and arrives at a "minimum" value below which you cannot scale down, and expects that you specify the value below this minimum value.

Note

  • When creating or scaling a VM Cluster, setting the number of OCPUs to zero will shut down the VM Cluster and eliminate any billing for that VM Cluster, but the hypervisor will still reserve the minimum 2 OCPUs for each VM. These reserved OCPUs cannot be allocated to any other VMs, even though the VM to which they are allocated is shut down. The Control Plane does not account for reserved OCPUs when showing maximum available OCPU, so you should account for these reserved OCPU when performing any subsequent scaling operations to ensure the operation can acquire enough OCPUs to successfully complete the operation.
  • For memory and /u02 scale up or scale down operations, if the difference between the current value and the new value is less than 2%, then no change will be made to that VM. This is because memory change involves rebooting the VM, and /u02 change involves bringing down the Oracle Grid Infrastructure stack and un-mounting /u02. Production customers will not resize for such a small increase or decrease, and hence such requests are a no-op.
  • You can scale down the following resources in any combinations:
    • OCPU
    • Memory
    • Local storage
    • Exadata storage

    Each scaling operation can take several minutes to complete. The time for each operation will vary based on activity in the system, but as a general rule, most operations should complete within 15 minutes for a quarter rack, 20 minutes for a half rack, and 30 minutes for a full or larger rack. Performing multiple OCPU scaling operations over a short period of time can lengthen the time for completion. Although online, OCPU scaling is not implemented on all VMs in parallel so as to detect and protect from any anomalies before they affect the entire system. Memory and Local Storage scaling require a VM reboot, and are performed one VM at a time in a rolling manner.

    If you run multiple scale-down operations, then each operation is performed serially. For example, if you scale memory and local storage from the Console, then the system will first scale memory, and when that operation completes, it will scale storage. The time to complete all operations will be the sum of the time to complete individual operations.

  • Storage servers added to the infrastructure but yet to run the 'Add Capacity' step will not have any disk groups created on them.

Resizing Memory and Large Pages

You can scale the database server memory up and down in a VM Cluster. Scaling memory requires a rolling restart of the database servers to take effect.

Changing the memory in a VM Cluster will affect the large pages (HugePages) settings for the VMs in that cluster. When a VM is initially created, each VM's operating system is configured with 50% of the memory allocated to the VM for large pages, and databases are configured to use that memory for their SGA. Oracle recommends that you not modify the large pages configuration unless you understand the implication of any changes you make. Improper configurations can prevent all databases from starting, and even prevent the VM from starting up.

Although not recommended, you are allowed to modify the large pages configuration. Any changes you make may be modified by automation should you subsequently resize the memory available to the VM. After a memory resize operation, the cloud automation will attempt to maintain the same amount of large pages memory as a percentage of the total memory, with a cap of 60%. If you configure large pages to be greater than 60% of total memory, then the cloud automation will resize it to 60% of total memory. This automatic resize is to ensure sufficient conventional memory for the virtual machine to start. The automation will perform a precheck to determine the actual large pages memory in use by the running database instances, and ensure after the resize that there is enough large pages memory available to support those same databases. If there will not be sufficient memory available after the resize, then the precheck will fail and the resize will not continue.

Calculating the ASM Storage

Use the following formula to calculate the minimum required ASM storage:

  • For each disk group, for example, DATA, RECO, note the total size and free size by running the asmcmd lsdg command on any Guest VM of the VM cluster.
  • Calculate the used size as (Total size - Free size) / 3 for each disk group. The /3 is used because the disk groups are triple mirrored.
  • DATA:RECO ratio is:

    80:20 if Local Backups option was NOT selected in the user interface.

    40:60 if Local Backups option was selected in the user interface.

  • Ensure that the new total size as given in the user interface passes the following conditions:

    Used size for DATA * 1.15 <= (New Total size * DATA % )

    Used size for RECO * 1.15 <= (New Total size * RECO % )

Example 5-2 Calculating the ASM Storage

  1. Run the asmcmd lsdg command in the Guest VM:
    • Without SPARSE:
      /u01/app/19.0.0.0/grid/bin/asmcmd lsdg
      ASMCMD>
      State   Type Rebal Sector Logical_Sector Block AU     Total_MB   Free_MB    Req_mir_free_MB   Usable_file_MB   Offline_disks    Voting_files   Name
      MOUNTED HIGH N        512     512        4096 4194304 12591936   10426224   1399104           3009040           0                       Y      DATAC5/
      MOUNTED HIGH N        512     512        4096 4194304 3135456    3036336    348384            895984            0                       N      RECOC5/
      ASMCMD>
    • With SPARSE:
      /u01/app/19.0.0.0/grid/bin/asmcmd lsdg
      ASMCMD>
      State   Type Rebal Sector Logical_Sector Block AU       Total_MB   Free_MB   Req_mir_free_MB   Usable_file_MB   Offline_disks    Voting_files   Name
      MOUNTED HIGH N        512     512        4096 4194304   12591936   10426224  1399104           3009040            0                       Y     DATAC5/
      MOUNTED HIGH N        512     512        4096 4194304   3135456    3036336   348384            895984             0                       N     RECOC5/
      MOUNTED HIGH N        512     512        4096 4194304   31354560   31354500  3483840           8959840            0                       N     SPRC5/
      ASMCMD>
    Note

    The listed values of all attributes for SPARSE diskgroup (SPRC5) present the virtual size. In Exadata DB Systems and Exadata Cloud Infrastructure, we use the ratio of 1:10 for physicalSize:virtualSize. Hence, for all purposes of our calculation we must use 1/10th of the values displayed above in case of SPARSE for those attributes.

  2. Used size for a disk group = (Total_MB - Free_MB) /3
    • Without SPARSE:

      Used size for DATAC5 = (12591936 - 10426224 ) / 3 = 704.98 GB

      Used size for RECO5 = (3135456 - 3036336 ) / 3 = 32.26 GB

    • With SPARSE:

      Used size for DATAC5 = (12591936 - 10426224 ) / 3 ~= 704.98 GB

      Used size for RECO5 = (3135456 - 3036336 ) /3 ~= 32.26 GB

      Used size for SPC5 = (1/10 * (31354560 - 31354500)) / 3 ~= 0 GB

  3. Storage distribution among diskgroups
    • Without SPARSE:

      DATA:RECO ratio is 80:20 in this example.

    • With SPARSE:

      DATA RECO: SPARSE ratio is 60:20:20 in this example.

  4. New requested size should pass the following conditions:
    • Without SPARSE: (For example, 5 TB in user interface.)

      5 TB = 5120 GB ; 5120 *.8 = 4096 GB; 5120 *.2 = 1024 GB

      For DATA: (704.98 * 1.15 ) <= 4096 GB

      For RECO: (32.36 * 1.15) <= 1024 GB

    • With SPARSE: (For example, 8 TB in the user interface.)

      8 TB = 8192 GB; 8192 *.6 = 4915 GB; 8192 *.2 = 1638 GB; 8192 *.2 = 1638 GB

      For DATA: (704.98 * 1.15 ) <= 4915 GB

      For RECO: (32.36 * 1.15) <= 1638 GB

      For SPR: (0 * 1.15) <= 1638 GB

Above resize will go through. If above conditions are not met by the new size, then resize will fail the precheck.

Estimating How Much Local Storage You Can Provision to Your VMs

Note

The following does not apply to Base Systems as they do not support multiple VMs. The Base System has 200 GB available for /u02.

X8M Systems

The maximum number of VMs per physical database server in an Exadata Cloud Infrastructure X8M will be 4. If there is not enough local disk space or other resources available the number of VMs that can be created will be less.

For an Exadata Database Service X8M system, the fixed consumption per VM image is 443 GB.

Total space available to all VMs on an ExaDB-D X8M databases node is 2243 GB. The amount of storage available for /u02 will be the total available space of 2243 GB less the 443 GB used for each VM image on the server. There is a 900 GB limit to any one /u02.

  • Total space available for VM images (X8M Qtr/Half/Full Racks): 2243 GB
  • Fixed storage per VM Image: 443 GB

Table 5-2 Space allocated to VMs

#VMs Fixed Storage All VMs (GB) X8M Space for All /u02 (GB)

1

443

900

2

886

1357

3

1329

914

4

1772

471

For an X8M, to get the max space available for /u02 for the nth VM, take the number in the table above and subtract anything previously allocated for /u02 to the other VMs. If you allocated 60 GB to VM1, 70 GB to VM2, 80 GB to VM3 (total 210 GB) in an X8M, the maximum available for VM 4 would be 471- 210 = 261 GB.

X9M Systems

The maximum number of VMs per physical database server in an Exadata Cloud Infrastructure X9M will be 4. If there is not enough local disk space or other resources available the number of VMs that can be created will be less.

For an Exadata Database Service X9M system, the fixed consumption per VM image is 443 GB.

Total space available to all VMs on an ExaDB-D X9M databases node is 2243 GB. The amount of storage available for /u02 will be the total available space of 2243 GB less the 443 GB used for each VM image on the server. There is a 900 GB limit to any one /u02.

  • Total Available for VM Images (Qtr/Half/Full Racks): 2243 GB
  • Fixed overhead per VM Image: 443 GB

Table 5-3 Space allocated to VMs

#VMs Fixed Storage All VMs (GB) X9M Space for All /u02 (GB)

1

443

900

2

886

1357

3

1329

914

4

1772

471

For an X9M, to get the max space available for /u02 for the nth VM, take the number in the table above and subtract anything previously allocated for /u02 to the other VMs. If you allocated 60 GB to VM1, 70 GB to VM2, 80 GB to VM3 (total 210 GB) in an X9M, the maximum available for VM 4 would be 471 - 210 = 261 GB.

Scaling Local Storage

Scale Local Space Operation Guidelines

The scaling local storage operation expects you to input a local space value that you want for the /u02 file system on each node.

  • Maximum size

    The maximum supported size of /u02 is 900 GB per VM. Depending on the number of other VMs in the system and the space consumed by those VMs, you may be subject to a lower maximum for /u02 due to limited space. Refer to tables 5-2 through 5-3.

  • Minimum size

    The minimum supported size of /u02 is 60 GB per VM.

  • Resource Limit Based On Current Utilization

    Any scale down operation must leave 15% buffer on top of highest local space utilization across all nodes in the cluster.

    The lowest local space per node allowed is higher of the above two limits.

    Run the df –kh command on each node to find out the node with the highest local storage.

    You can also use the utility like cssh to issue the same command from all hosts in a cluster by typing it just once.

    Lowest value of local storage each node can be scaled down to would be = 1.15x (highest value of local space used among all nodes).

  • A rolling restart of each VM is required to resize /u02.

If requested by support, you can also resize the /acfs01 file system. This file system is used by the system to stage software. It uses Exadata storage and is not subject to the limits described above for /u02. It is a shared file system visible from all nodes in the cluster, and can be online resized from the command line of any VM.

  • Default size: The default size of /acfs01 is 100 GB.
  • Scaling /acfs01: You can scale acfs01 as user grid from any VM via the /sbin/acfsutil command. No reboot is required. The resize operation will not affect the availability of the database service running in the VM Cluster. The following command issued by the grid user will increase the size of /acfs01 by 100 GB: /sbin/acfsutil size +100 GB /acfs01.

Overview of VM Cluster Node Subsetting

VM Cluster Node Subsetting enables you to allocate a subset of database servers to new VM clusters to enable maximum flexibility in the allocation of compute (CPU, memory, local storage) resources.

With VM Cluster Node Subsetting, you can:
  • Create a smaller VM cluster to host databases that have low resource and scalability requirements or to host a smaller number of databases that require isolation from the rest of the workload.
  • Expand or shrink an existing VM cluster by adding and removing nodes to ensure optimal utilization of available resources.
Consider reviewing the points below that will assist you in subsetting VM cluster nodes.
  • VM Cluster Node Subsetting capability is available for new VM clusters in Oracle Exadata Database Service on Dedicated Infrastructure service.
  • All VMs across a VM cluster will have the same resource allocation per VM irrespective of whether the VM was created during cluster provisioning or added later by extending an existing VM cluster.
  • Any VM cluster must have a minimum of 2 DB servers.
  • You can host a maximum of 4 VMs on X8M and above generations of DB Servers.
  • Exadata Infrastructures with X8M and above generation of DB Servers can support a maximum of 8 VM clusters across all DB Servers.
  • Maximum number of clusters across the infrastructure depends on the resources available per DB server and is subject to the per DB Server maximum VM limit.

With the release of Multi-VM, the add and remove virtual machine api for cloud vm clusters will not be supported via terraform.

You can perform these operations through UI, SDK, OCI CLI, OCI Ansible or similar tools. Terraform states should be managed similar to other operations which happen outside of terraform but need to be managed in terraform.

For more information, see Detecting and Managing Drift with Terraform.

Add a VM to a VM Cluster

Add a Virtual Machine to a VM Cluster

Note

Once the VM cluster is upgraded to Exadata Database Service Guest VM OS 23.1, you will be able to add a new VM or a new database server to this VM cluster if Exadata Cloud Infrastructure is running an Exadata System Software version 22.1.16 and later.

Upgrade to Exadata System Software 23.1 for Exadata Cloud Infrastructure will be available with February 2023 update cycle.

Note

  • This operation is only available with Multi-VM enabled Infrastructure.
  • To add a VM to a VM Cluster requires that all TCP ports to be open for the client subnet CIDR for ingress and egress.
  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that contains the VM cluster for which you want to scale the CPU resources.
  3. Click VM Clusters.
  4. Click the name of the VM cluster to which you want to add a virtual machine.
  5. Under Resources, select Virtual Machines, and click the Add Virtual Machines button.
  6. In the Add Virual Machines window, select the DB server where you want the new VM to reside.
    Note

    The VM that is added will have the same resources as the other VMs in the cluster.
  7. Click Add Virtual Machine.
Note

Add a VM to a VM Cluster is NOT supported using Terraform.

Terminate a VM from a VM Cluster

To remove a virtual machine from a provisioned cluster, use this procedure.

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that contains the VM cluster for which you want to scale the CPU resources.
  3. Click VM Clusters.
  4. Click the name of the VM cluster for which you want to remove a virtual machine.
  5. On the Exadata VM Cluster Details page, in the Virtual Machines section, select the Virtual Machine that will be removed, click the more commands symbol (three dots) and click Terminate
Note

Remove a VM from a VM Cluster is NOT supported using Terraform at this time.

About Application VIP

Oracle Exadata Database Service on Dedicated Infrastructure fully supports creating additional Virtual IP Addresses on an Exadata VM Cluster.

These application VIPs are required to protect additional applications such as Oracle GoldenGate installed on an Oracle Exadata Database Service on Dedicated Infrastructure system or other services such as XA-Agents, and to provide High Availability to these additional applications. For more information, see Oracle Grid Infrastructure Standalone Agents for Oracle Clusterware and Making Applications Highly Available Using Oracle Clusterware.

Within the Oracle Cloud Infrastructure, adding Virtual IP Addresses on the cluster stack alone is not sufficient as these additional (secondary) IP addresses also have to be added to the VCN layer as “Floating IP” addresses so that the VCN layer knows where these IP addresses are running, and in case of failover by the Clusterware to change the VNIC the floating IP address is attached to. For more information, see Creating an Application VIP Managed by Oracle Clusterware and Overview of IP Addresses.

Adding an Application VIP to an Exadata VM Cluster consists of the following steps:

  1. Add the Virtual IP address to the Clusterware layer within the Exadata DomU, by following the standard Oracle Clusterware documentation, or the guide provided by the application, for example, by using
    appvipcfg create -network=1 -ip=10.10.10.10
              -vipname=applicationvip
    .
  2. Attach the Application Floating IP address object on the Exadata VM Cluster to add the knowledge of the floating IP to the VCN layer. Ensure that you choose the same subnet as you created the backend application VIP, which normally is the client subnet.

    The private IP address needs to be the same as the one specified in the appvipcfg command above. The Virtual IP Address Hostname is the name under which the IP address is reachable via DNS and does not have to be the same as the vipname.

    If you have already started the VIP in the backend, ensure that the Virtual Machine Name reflects the host on which the VIP was started in the backend.

  3. Test the relocation of the VIP. The VIP should stay available (test this via. ping), and the user interface should display after a short while that the floating IP also has moved to another host.

    If you did choose the wrong host while creating the VCN attachment, then simply relocate the VIP within the cluster. The VCN layer will detect the change and the user interface should get updated after a short while.

Note

A single Virtual VM Cluster has a limitation of 8 additional Application VIPs. The limitation exists because a single VNIC can only have 31 additional secondary IP addresses. For more information, see Overview of IP Addresses. If all VIPs are started on the same node, then the application VIPs cannot be reached.

If more application VIPs are required, then raise an SR to have this limit increased. However, there are a few additional steps required then, to ensure that under no scenario more than 31 secondary IP addresses are attached to a single Exadata VM Cluster node. One way to accomplish this would be to ensure application VIPs are bound by the Clusterware to certain nodes so that this scenario is prevented.

A setup with 32 additional application VIPs would look as follows:

Floating IP Node 1 Node 2 Node 3 Node 4
Private Hostname 1 1 1 1
VIP Hostname 4 4 4 4
SCAN 3 3 3 3
Appvip 1-8 8 8 - -
Appvip 9-16 - 8 8 -
Appvip 17-24 - - 8 8
Appvip 25-32 8 - - 8
Max Possible VIP if all Floating IPs failover 24 24 24 24

Using the Console to Manage VM Clusters on Exadata Cloud Infrastructure

Learn how to use the console to create, edit, and manage your VM Clusters on Oracle Exadata Database Service on Dedicated Infrastructure.

Create a VM cluster in an Exadata Cloud Infrastructure instance.

Note

To create a cloud VM cluster in an Exadata Cloud Infrastructure instance, you must have first created a Cloud Exadata infrastructure resource.

Note

Multi-VM enabled Infrastructure will support creating multiple VM Clusters. Infrastructures created before the feature Create and Manage Multiple Virtual Machines per Exadata System (MultiVM) and VM Cluster Node Subsetting was released only support creating a single cloud VM cluster.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters.
    Note

    Multiple VM clusters may be created only in a Multi-VM enabled Infrastructure.
  3. Click Create Exadata VM Cluster.

    The Create Exadata VM Cluster page is displayed. Provide the required information to configure the VM cluster.

  4. Compartment: Select a compartment for the VM cluster resource.
  5. Display name: Enter a user-friendly display name for the VM cluster. The name doesn't need to be unique. An Oracle Cloud Identifier (OCID) will uniquely identify the DB system. Avoid entering confidential information.
  6. Select Exadata infrastructure: Select the infrastructure resource that will contain the VM cluster. You must choose an infrastructure resource that has enough resources to create a new VM cluster. Click Change Compartment and pick a different compartment from the one you are working in to view infrastructure resources in other compartments.
    Note

    Multiple VM clusters may be created only in a Multi-VM enabled Infrastructure
  7. Choose the Oracle Grid Infrastructure version: From the list, choose the Oracle Grid Infrastructure release that you want to install on the VM cluster.

    The Oracle Grid Infrastructure release determines the Oracle Database releases that can be supported on the VM cluster. You cannot run an Oracle Database release that is later than the Oracle Grid Infrastructure software release.

  8. Choose an Exadata image version:
    • Exadata infrastructure with Oracle Linux 7 and Exadata image version 22.1.10.0.0.230422:
      • The Change image button is not enabled.
      • The Oracle Grid Infrastructure version defaults to 19.0.0.0.0.
      • The Exadata guest version will be the same as that of the host OS.
    • Exadata infrastructure with Oracle Linux 8 and Exadata image version 23.1.3.0.0.230613:
      • The Exadata guest version defaults to the latest (23.1.3.0).
      • The Oracle Grid Infrastructure version defaults to 19.0.0.0.0
      • The Change image button is enabled.
      • Click Change image.

        The resulting Change image panel displays the list of available major versions of Exadata image (23.1.3.0 and 22.1.3.0).

        The most recent release for each major version is indicated by "(latest)".

      • Slide Display all available versions.

        Six past versions including the latest versions of Exadata images 23.1.3.0 and 22.1.3.0 are displayed.

      • Choose a version.
      • Click Save Changes.
  9. Configure the VM cluster: Specify the DB servers to used for new VM cluster (by default all DB Servers are selected). Click Change DB Servers to select from the available DB servers. In the Resource allocation per VM pane:
    • Specify the number of OCPU cores you want to allocate to each of the VM cluster's virtual machine compute nodes. Minimum is 2 OCPU per VM . The read-only Requested OCPU count for the Exadata VM cluster field displays the total number of OCPU cores you are allocating.
    • Specify the Memory per VM to allocate to each VM. The minimum per VM is 30 GB.
    • Specify the Local Storage per VM to allocate local storage to each VM. The minimum per VM is 60 GB.
  10. Configure Exadata storage: Specify the following:
    • Specify the usable Exadata storage TB. Specify the storage in multiples of 1 TB. Minimum: 2 TB
    • Allocate storage for Exadata sparse snapshots: Select this configuration option if you intend to use snapshot functionality within your VM cluster. If you select this option, the SPARSE disk group is created, which enables you to use VM cluster snapshot functionality for PDB sparse cloning. If you do not select this option, the SPARSE disk group is not created and snapshot functionality will not be available on any database deployments that are created in the environment.
      Note

      The storage configuration option for sparse snapshots cannot be changed after VM cluster creation.
    • Allocate storage for local backups: Select this option if you intend to perform database backups to the local Exadata storage within your Exadata Cloud Infrastructure instance. If you select this option, more space is allocated to the RECO disk group, which is used to store backups on Exadata storage. If you do not select this option, more space is allocated to the DATA disk group, which enables you to store more information in your databases.
      Note

      The storage configuration option for local backups cannot be changed after VM cluster creation.
  11. Add SSH key: Add the public key portion of each key pair you want to use for SSH access to the DB system:
    • Generate SSH key pair (Default option) Select this radio button to generate an SSH keypair. Then in the dialog below click Save private key to download the key, and optionally click Save public key to download the key.
    • Upload SSH key files: Select this radio button to browse or drag and drop .pub files.
    • Paste SSH keys: Select this radio button to paste in individual public keys. To paste multiple keys, click + Another SSH Key, and supply a single key for each entry.
  12. Configure the network settings: Specify the following:

    Note

    IP addresses (100.64.0.0/10) are used for Exadata Cloud Infrastructure X8M interconnect.
    • Virtual cloud network: The VCN in which you want to create the VM cluster. Click Change Compartment to select a VCN in a different compartment.
    • Client subnet: The subnet to which the VM cluster should attach. Click Change Compartment to select a subnet in a different compartment.

      Do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet causes the private interconnect to malfunction.

    • Backup subnet: The subnet to use for the backup network, which is typically used to transport backup information to and from the Backup Destination, and for Data Guard replication. Click Change Compartment to select a subnet in a different compartment, if applicable.

      Do not use a subnet that overlaps with 192.168.128.0/20. This restriction applies to both the client subnet and backup subnet.

      If you plan to back up databases to Object Storage or Autonomous Recovery service, see the network prerequisites in Managing Exadata Database Backups.

    • Network Security Groups: Optionally, you can specify one or more network security groups (NSGs) for both the client and backup networks. NSGs function as virtual firewalls, allowing you to apply a set of ingress and egress security rules to your Exadata Cloud Infrastructure VM cluster. A maximum of five NSGs can be specified. For more information, see Network Security Groups and Network Setup for Exadata Cloud Infrastructure Instances.

      Note that if you choose a subnet with a security list, the security rules for the VM cluster will be a union of the rules in the security list and the NSGs.

      To use network security groups:

      • Check the Use network security groups to control traffic check box. This box appears under both the selector for the client subnet and the backup subnet. You can apply NSGs to either the client or the backup network, or to both networks. Note that you must have a virtual cloud network selected to be able to assign NSGs to a network.
      • Specify the NSG to use with the network. You might need to use more than one NSG. If you're not sure, contact your network administrator.
      • To use additional NSGs with the network, click +;Another Network Security Group.
    • To use private DNS Service
      Note

      A Private DNS must be configured before it can be selected. See Configure Private DNS
      • Check the Use private DNS Service check box.
      • Select a private view. Click Change Compartment to select a private view in a different compartment.
      • Select a private zone. Click Change Compartment to select a private zone in a different compartment.
    • Hostname prefix: Your choice of hostname for the Exadata DB system. The host name must begin with an alphabetic character and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed for an Exadata DB system is 12.

      Caution:

      The hostname must be unique within the subnet. If it is not unique, the VM cluster will fail to provision.
    • Host domain name: The domain name for the VM cluster. If the selected subnet uses the Oracle-provided Internet and VCN Resolver for DNS name resolution, this field displays the domain name for the subnet and it can't be changed. Otherwise, you can provide your choice of the domain name. Hyphens (-) are not permitted.

      If you plan to store database backups in Object Storage or Autonomous Recovery service, Oracle recommends that you use a VCN Resolver for DNS name resolution for the client subnet because it automatically resolves the Swift endpoints used for backups.

    • Host and domain URL: This read-only field combines the host and domain names to display the fully qualified domain name (FQDN) for the database. The maximum length is 63 characters.
  13. Choose a license type: The type of license you want to use for the VM cluster. Your choice affects metering for billing.

    • License Included means the cost of the cloud service includes a license for the Database service.
    • Bring Your Own License (BYOL) means you are an Oracle Database customer with an Unlimited License Agreement or Non-Unlimited License Agreement and want to use your license with Oracle Cloud Infrastructure. This removes the need for separate on-premises licenses and cloud licenses.
  14. Diagnostics Collection: By enabling diagnostics collection and notifications, Oracle Cloud Operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to Events to get notified about resource state changes.
    Note

    You are opting in with the understanding that the above list of events (or metrics, log files) can change in the future. You can opt out of this feature at any time.
    • Enable Diagnostic Events: Allow Oracle to collect and publish critical, warning, error, and information events to me.
    • Enable Health Monitoring: Allow Oracle to collect health metrics/events such as Oracle Database up/down, disk space usage, and so on, and share them with Oracle Cloud operations. You will also receive notification of some events.
    • Enable Incident Logs and Trace Collection: Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution.

    Note

    You are opting in with the understanding that the above list of events (or metrics, log files) can change in the future. You can opt-out of this feature at any time.
    All three checkboxes are selected by default. You can leave the default settings as is or clear the checkboxes as needed. You can view the Diagnostic Collection settings on the VM Cluster Details page under General Information >> Diagnostics Collection.
    • Enabled: When you choose to collect diagnostics, health metrics, incident logs, and trace files (all three options).

    • Disabled: When you choose not to collect diagnostics, health metrics, incident logs, and trace files (all three options).

    • Partially Enabled: When you choose to collect diagnostics, health metrics, incident logs, and trace files ( one or two options).
  15. Click Show Advanced Options to specify advanced options for the VM cluster:

    • Time zone: This option is located in the Management tab. The default time zone for the DB system 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. For more information, see DB System Time Zone .

      Note

      If you want to set a time zone other than UTC or the browser-detected time zone, and if you do not see the time zone you want, try selecting the Select another time zone, option, then selecting "Miscellaneous" in the Region or country list and searching the additional Time zone selections.

    • SCAN Listener Port: This option is located in the Network tab. You can assign a SCAN listener port (TCP/IP) in the range between 1024 and 8999. The default is 1521
      Note

      Manually changing the SCAN listener port of a VM cluster after provisioning using the backend software is not supported. This change can cause Data Guard provisioning to fail.
      .
    • Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags . If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
  16. Click Create Exadata VM Cluster.

WHAT NEXT?

After your VM cluster is successfully created and in the Available state, you can view the VM Cluster Details page by clicking the name of the VM cluster in the list of clusters. From the VM Cluster Details page, you can create your first database in the cluster by clicking Create Database.

To add database server or storage server capacity to a cloud VM cluster

This topic describes how to use the Oracle Cloud Infrastructure (OCI) Console to add the new capacity to your cloud VM cluster.

Note

This procedure does not apply to Multi-VM enabled Infrastructure

If you have used the task To add compute and storage resources to a flexible cloud Exadata infrastructure resource by adding additional database (compute) or storage servers to the service instance, you must add the additional capacity to the cloud VM cluster to utilize the additional resources.

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters.
  3. In the list of cloud VM clusters, click the name of the cluster to which you want to add capacity.
  4. On the VM Cluster Details page, click Scale VM Cluster.
  5. If you have additional capacity available as a result of scaling the cloud Exadata infrastructure resource, a banner at the top of the Scale VM Cluster panel provides a message telling you the type and amount of additional capacity available to the VM cluster. Check the Add Capacity box.
  6. Select either the Add Database Server or the Add Storage radio button, depending on which type of capacity you want to add to the cloud VM cluster.
  7. Click Update. The cloud VM cluster goes into the Updating state. When the capacity has been successfully added, the cluster returns to the Available state.
Note

If you have added additional database servers to the cluster, you can allocate the new CPU cores once the cluster is in the Available state by clicking the Scale VM Cluster button again. See To scale CPU cores in an Exadata Cloud Service cloud VM cluster or DB system for more information on adding CPU cores to your cloud VM cluster.

Using the Console to Enable, Partially Enable, or Disable Diagnostics Collection

You can enable, partially enable, or disable diagnostics collection for your Guest VMs after provisioning the VM cluster. Enabling diagnostics collection at the VM cluster level applies the configuration to all the resources such as DB home, Database, and so on under the VM cluster.

Note

  • You are opting in with the understanding that the list of events, metrics, and log files collected can change in the future. You can opt-out of this feature at any time.
  • Oracle may add more metrics in the future, but if you have already chosen to collect metrics, you need not update your opt-in value. It will remain enabled/disabled based on your current preference.
  • If you have previously opted in for incident log and trace file collection and decide to opt out when Oracle Cloud operations run a log collection job, then the job will run its course and will not cancel. Future log collections won't happen until you opt-in again to the incident logs and trace file collection option.
  1. Open the navigation menu. Under Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region that contains your Exadata infrastructure.
  3. Click VM Clusters.
  4. Click the name of the VM cluster you want to enable or disable diagnostic data collection.
  5. On the VM Cluster Details page, under General Information, enable, partially enable, or disable Diagnostics Collection beside Diagnostics Collection.
  6. In the Edit Diagnostics Collection Settings dialog, enable or disable any of the Diagnostics Collections. By enabling diagnostics collection and notifications, Oracle Cloud Operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to Events to get notified about resource state changes.
    • Enable Diagnostics Events Allow Oracle to collect and publish critical, warning, error, and information events to me. For more information, see Overview of Database Service Events
    • Enable Health Monitoring Allow Oracle to collect health metrics/events such as Oracle Database up/down, disk space usage, and so on, and share them with Oracle Cloud operations. You will also receive notification of some events.
    • Enable Incident logs and trace collection. Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution.

      Note: You had previously opted in for incident log and trace file collection and decide to opt-out when Oracle Cloud operations run a log collection job, the job will run its course and will not cancel. Future log collections will not run until you opt-in again to the incident logs and trace file collection option.

  7. Select or clear the checkboxes and then click Save Changes.

Using the Console to Update the License Type on a VM Cluster

To modify licensing, be prepared to provide values for the fields required for modifying the licensing information.

  1. Open the navigation menu. Under Oracle Database, click Exadata Cloud Infrastructure.
  2. Choose the Region and Compartment that contains the VM cluster for which you want to update the license type.
  3. Click VM Clusters.
  4. Click the name of the VM cluster for which you want to update the license type.

    The VM Cluster Details page displays information about the selected VM cluster.

  5. Click Update License Type.
  6. In the dialog box, choose one of the following license types and then click Save Changes.
    • 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 Cloud Infrastructure.

    Updating the license type does not change the functionality or interrupt the operation of the VM cluster.

To add SSH keys to a VM cluster

The VM cluster exists, and you wish to add a another user which requires another SSH key.

  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Click Exadata VM Clusters.
  4. In the list of VM clusters, find the cluster you want to manage and click its highlighted name.
  5. Click Add SSH Keys.
  6. Select one of the following options:
    • Generate SSH key pair: Use this option to create a new SSH key pair. Click both Save Private Key and Save Public Key when using this option. The private key is downloaded to your local machine, and should be stored in a safe location. You cannot download another copy of the private key generated during this operation after completing the operation.

    • Upload SSH key files: Select this option to browse or drag and drop .pub files.

    • Paste SSH keys: Select this option to paste in individual public keys. To paste multiple keys, click + Another SSH Key, and supply a single key for each entry.

  7. Click Save Changes.

Using the Console to Add SSH Keys After Creating a VM Cluster

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Click VM Clusters.
  3. Click the name of the VM cluster that you want to add SSH key(s).
  4. In the VM Cluster Details page, click Add SSH Keys.
  5. In the ADD SSH Keys dialog, choose any one of the methods:
    • Generate SSH key pair: Select this option if you want the Control Plane to generate public/private key pairs for you.

      Click Save Private Key and Save Public Key to download and save SSH Key pair.

    • Upload SSH key files: Select this option to upload the file that contains SSH Key pair.
    • Paste SSH keys: Select this option to paste the SSH key string.

      To provide multiple keys, click Another SSH Key. For pasted keys, ensure that each key is on a single, continuous line. The length of the combined keys cannot exceed 10,000 characters.

  6. Click Save Changes.

Using the Console to Stop, Start, or Reboot a VM Cluster Virtual Machine

Use the console to stop, start, or reboot a virtual machine.

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that is associated with the VM cluster that contains the virtual machine that you want to stop, start, or reboot.
  3. Click VM Clusters.
  4. Click the name of the VM cluster that contains the virtual machine that you want to stop, start, or reboot.

    The VM Cluster Details page displays information about the selected VM cluster.

  5. In the Resources list, click Virtual Machines.

    The list of virtual machines is displayed.

  6. In the list of nodes, click the Actions icon (three dots) for a node, and then click one of the following actions:
    1. Start: Restarts a stopped node. After the node is restarted, the Stop action is enabled.
    2. Stop: Shuts down the node. After the node is stopped, the Start action is enabled.
    3. Reboot: Shuts down the node, and then restarts it.

Using the Console to Check the Status of a VM Cluster Virtual Machine

Review the health status of a VM cluster virtual machine.

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that is associated with the VM cluster that contains the virtual machine that you are interested in.
  3. Click VM Clusters.
  4. Click the name of the VM cluster that contains the virtual machine that you are interested in.

    The VM Cluster Details page displays information about the selected VM cluster.

  5. In the Resources list, click Virtual Machines.

    The list of virtual machines displays. For each virtual machine in the VM cluster, the name, state, and client IP address are displayed.

  6. In the node list, find the virtual machine that you are interested in and check its state.

    The color of the icon and the associated text it indicates its status.

    • Available: Green icon. The node is operational.
    • Starting: Yellow icon. The node is starting because of a start or reboot action in the Console or API.
    • Stopping: Yellow icon. The node is stopping because of a stop or reboot action in the Console or API.
    • Stopped: Yellow icon. The node is stopped.
    • Failed: Red icon. An error condition prevents the continued operation of the virtual machine.

Using the Console to Move a VM Cluster to Another Compartment

To change the compartment that contains your VM cluster on Exadata Cloud Infrastructure, use this procedure.

When you move a VM cluster, the compartment change is also applied to the virtual machines and databases that are associated with the VM cluster. However, the compartment change does not affect any other associated resources, such as the Exadata infrastructure, which remains in its current compartment.

  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that contains the VM cluster that you want to move.
  3. Click VM Clusters.
  4. Click the name of the VM cluster that you want to move.

    The VM Cluster Details page displays information about the selected VM cluster.

  5. Click Move Resource.
  6. In the resulting dialog, choose the new compartment for the VM cluster, and click Move Resource.

To change the VM cluster display name

Using the Console to Terminate a VM Cluster

Before you can terminate a VM cluster, you must first terminate the databases that it contains.

Terminating a VM cluster removes it from the Cloud Control Plane. In the process, the virtual machines and their contents are destroyed.
Note

You cannot terminate a VM cluster from an infrastructure with less than 5 storage servers
  1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region and Compartment that contains the VM cluster that you want to terminate.
  3. Click VM Clusters.
  4. Click the name of the VM cluster that you want to terminate.

    The VM Cluster Details page displays information about the selected VM cluster.

  5. Click More Actions, and then click Terminate.
  6. In the resulting dialog:
    • Review the message about the backup retention policy
    • Enter the name of the VM cluster
    • Click Terminate VM Cluster to confirm the action.
    Note

    The database stays in a terminated state with backups listed until all backups are expired.

To view details about private DNS configuration

  1. Open the navigation menu. Under Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region that contains your Exadata infrastructure.
  3. Choose the Compartment that contains your Exadata infrastructure.
  4. Click VM Clusters.
  5. Click the name of the VM cluster that is configured with a private DNS you want to view.
  6. Under the Network section, Private DNS and Private Zone are displayed, if a private DNS is configured.
  7. Click the Private View name to edit the configuration.

To Attach a Virtual IP Address

Attach a Virtual IP address from a VM cluster using this procedure.

  1. Open the navigation menu. Under Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region that contains your Exadata infrastructure.
  3. Choose the Compartment that contains your Exadata infrastructure.
  4. Click VM Clusters.
  5. Under the Resources, click Virtual IP Address.
  6. Click Attach Virtual IP Address.
  7. In the Attach Virtual IP Address dialog:
    1. Select a subnet from the Subnet drop-down list.
    2. Enter a hostname for the Virtual IP Address in the Virtual IP Address Hostname field.
    3. (Optional) Enter an IP address in the Virtual IP address field.
    4. (Optional) You can enter a VIrtual Machine name to be the default attachment in the Virtual Machine field.
    5. Click Attach.

To Detach a Virtual IP Address

Attach a Virtual IP address from a VM cluster using this procedure.

  1. Open the navigation menu. Under Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose the Region that contains your Exadata infrastructure.
  3. Choose the Compartment that contains your Exadata infrastructure.
  4. Click VM Clusters.
  5. Under the Resources, click Virtual IP Address.
  6. Click the Actions icon (three dots) to the right of the Virtual IP Address you wish to detach.
  7. Click Detach.
  8. In the Detach Virtual IP Address dialog, confirm by entering the VIP Address that you wish to detach and click Detach.

Overview of Automatic Diagnostic Collection

By enabling diagnostics collection and notifications, Oracle Cloud Operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to Events to get notified about resource state changes.

  • Enable Diagnostic Events

    Allow Oracle to collect and publish critical, warning, error, and information events to you. For more information, see Database Service Events.

  • Enable Health Monitoring

    Allow Oracle to collect health metrics/events such as Oracle Database up/down, disk space usage, and so on, and share them with Oracle Cloud operations. You will also receive notification of some events. For more information, see Health Metrics.

  • Enable Incident Logs and Trace Collection

    Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution. For more information, see Incident Logs and Trace Files.

Diagnostics Collection is:

  • Enabled: When you choose to collect diagnostics, health metrics, incident logs, and trace files (all three options).
  • Disabled: When you choose not to collect diagnostics, health metrics, incident logs, and trace files (all three options).
  • Partially Enabled: When you choose to collect diagnostics, health metrics, incident logs, and trace files (one or two options).

Disabling diagnostic events and health monitoring will only stop the collection and notification of data/events from the time you uncheck the checkboxes tied to the options. However, historical data will not be purged from Oracle Cloud Operations data repositories.

Incident Logs and Trace Files

This section lists all of the files that can be collected by Oracle Support if you opt-in for incident logs and trace collection.

Note

  • Oracle will create a service request (SR) against the infrastructure Customer Support Identifier (CSI) when an issue is detected and needs customer interaction to resolve.
  • The customer's Oralce CLoud Infrastructure tenancy admin email will be used as the CSI contact to create SR and attach logs to it. Ensure tenancy admin is added as a CSI contact in My Oracle Support (MOS).

Oracle Trace File Analyze (TFA) Component Driven Logs Collections

The directories are generally assigned to a component and that component can then be used to guide TFA to the files it needs to collect, for example, requesting the CRS component would tell TFA to look at directories mapped to the CRS component and find files that match the required collection time frame.

Note

If have previously opted in for incident log and trace file collection and decide to opt out when Oracle Cloud operations run a log collection job, then the job will run its course and will not cancel. Future log collections won't happen until you opt-in again to the incident logs and trace file collection option.

TFA is shipped with scripts that run when a particular component is requested, for example, for CRS component, crscollect.pl will run a number of crsctl commands and gather the input. By default, TFA does not redact collected logs.

Table 5-4 Oracle Trace File Analyze (TFA) Component Driven Logs Collections

Component Script Files/Directories

OS: Operating system logs

oscollect.pl

  • /var/log/messages
  • OSWatcher archive
  • Exadata Only: ExaWatcher archive

    /opt/oracle.ExaWatcher/archive/

CRS: Grid Infrastructure and cluster logs

crscollect.pl

  • /etc/oracle
  • GIHOME/crf/db/HOSTNAME1
  • GIHOME/crs/log
  • GIHOME/css/log
  • GIHOME/cv/log
  • GIHOME/evm/admin/log
  • GIHOME/evm/admin/logger
  • GIHOME/evm/log
  • GIHOME/log/-/client
  • GIHOME/log/HOSTNAME1
  • GIHOME/log/HOSTNAME1/admin
  • GIHOME/log/HOSTNAME1/client
  • GIHOME/log/HOSTNAME1/crflogd
  • GIHOME/log/HOSTNAME1/crfmond
  • GIHOME/log/HOSTNAME1/crsd
  • GIHOME/log/HOSTNAME1/cssd
  • GIHOME/log/HOSTNAME1/ctssd
  • GIHOME/log/HOSTNAME1/diskmon
  • GIHOME/log/HOSTNAME1/evmd
  • GIHOME/log/HOSTNAME1/gipcd
  • GIHOME/log/HOSTNAME1/gnsd
  • GIHOME/log/HOSTNAME1/gpnpd
  • GIHOME/log/HOSTNAME1/mdnsd
  • GIHOME/log/HOSTNAME1/ohasd
  • GIHOME/log/HOSTNAME1/racg
  • GIHOME/log/HOSTNAME1/srvm
  • GIHOME/log/HOSTNAME1/xag
  • GIHOME/log/diag/asmtool
  • GIHOME/log/diag/clients
  • GIHOME/log/procwatcher/PRW_SYS_HOSTNAME1
  • GIHOME/network/log
  • GIHOME/opmn/logs
  • GIHOME/racg/log
  • GIHOME/scheduler/log
  • GIHOME/srvm/log
  • GRIDBASE/crsdata/@global/cvu
  • GRIDBASE/crsdata/HOSTNAME1/core
  • GRIDBASE/crsdata/HOSTNAME1/crsconfig
  • GRIDBASE/crsdata/HOSTNAME1/crsdiag
  • GRIDBASE/crsdata/HOSTNAME1/cvu
  • GRIDBASE/crsdata/HOSTNAME1/evm
  • GRIDBASE/crsdata/HOSTNAME1/output
  • GRIDBASE/crsdata/HOSTNAME1/ovmmwallets
  • GRIDBASE/crsdata/HOSTNAME1/scripts
  • GRIDBASE/crsdata/HOSTNAME1/trace
  • GRIDBASE/diag/crs/-/crs/cdump
  • GRIDBASE/diag/crs/HOSTNAME1/crs/cdump
  • GRIDBASE/diag/crs/HOSTNAME1/crs/incident
  • GRIDBASE/diag/crs/HOSTNAME1/crs/trace

Database: Oracle Database logs

No DB Specific Script - runs opatch lsinventory for the ORACLE_HOME the DB runs from TFA will run ipspack based on the time range for certain DB incidents.

  • ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/cdump
  • ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/trace
  • ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/incident

Cloud Tool Logs

  • Creg files: /var/opt/oracle/creg/*.ini files with masked sensitive info
  • Cstate file: /var/opt/oracle/cstate.xml
  • Database related tooling logs:

    If dbName specified, /var/opt/oracle/log/<dbName>, else collect logs for all databases /var/opt/oracle/log/

    If dbName specified, /var/opt/oracle/dbaas_acfs/log/<dbName>, else collect logs for all databases /var/opt/oracle/log/<dbName>

  • Database env files: If dbName specified, /home/oracle/<dbName>.env, else collect logs for all databases /home/oracle/*.env
  • Pilot logs: /home/opc/.pilotBase/logs
  • List of log directories:
    • /var/opt/oracle/log
    • /var/opt/oracle/dbaas_acfs/log
    • /var/opt/oracle/dbaas_acfs/dbsystem_details
    • /var/opt/oracle/dbaas_acfs/job_manager
    • /opt/oracle/dcs/log

DCS Agent Logs

  • /opt/oracle/dcs/log/

Tooling-Related Grid Infrastructure/Database Logs

  • Grid Infrastructure: GI_HOME/cfgtoollogs
  • Database alertlog: /u02/app/oracle/diag/rdbms/*/*/alert*.log

Health Metrics

Review the list of database and non-database health metrics collected by Oracle Trace File Analyzer.

Note

Oracle may add more metrics in the future, but if you have already chosen to collect metrics, you need not update your opt-in value. It will remain enabled/disabled based on your current preference.

Guest VM Health Metrics List - Database Metrics

Table 5-5 Guest VM Health Metrics List - Database Metrics

Metric Name Metric Display Name Unit Aggregation Interval Collection Frequency Description

CpuUtilization

CPU Utilization

Percentage

Mean

One minute

Five minutes

The CPU utilization is expressed as a percentage, which is aggregated across all consumer groups. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use, which is two times the number of OCPUs.

StorageUtilization

Storage Utilization

Percentage

Mean

One hour

One hout

The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces.

BlockChanges

DB Block Changes

Changes per second

Mean

One minute

Five minutes

The Average number of blocks changed per second.

ExecuteCount

Execute Count

Count

Sum

One minute

Five minutes

The number of user and recursive calls that executed SQL statements during the selected interval.

CurrentLogons

Current Logons

Count

Sum

One minute

Five minutes

The number of successful logons during the selected interval.

TransactionCount

Transaction Count

Count

Sum

One minute

Five minutes

The combined number of user commits and user rollbacks during the selected interval.

UserCalls

User Calls

Count

Sum

One minute

Five minutes

The combined number of logons, parses, and execute calls during the selected interval.

ParseCount

Parse Count

Count

Sum

One minute

Five minutes

The number of hard and soft parses during the selected interval.

StorageUsed

Storage Space Used

GB

Max

One hour

One hour

Total amount of storage space used by the database at the collection time.

StorageAllocated

Storage Space Allocated

GB

Max

One hour

One hour

Total amount of storage space allocated to the database at the collection time.

StorageUsedByTablespace

Storage Space Used By Tablespace

GB

Max

One hour

One hour

Total amount of storage space used by tablespace at the collection time. In the case of container databases, this metric provides root container tablespaces.

StorageAllocatedByTablespace

Allocated Storage Space By Tablespace

GB

Max

One hour

One hour

Total amount of storage space allocated to the tablespace at the collection time. In the case of container databases, this metric provides root container tablespaces.

StorageUtilizationByTablespace

Storage Space Utilization By Tablespace

Percentage

Mean

One hour

One hour

This indicates the percentage of storage space utilized by the tablespace at the collection time. In the case of container databases, this metric provides root container tablespaces.

Guest VM Health Metrics List - Non-Database Metrics

Table 5-6 Guest VM Health Metrics List - Non-Database Metrics

Metric Name Metric Display Name Unit Aggregation Collection Frequency Description

ASMDiskgroupUtilization

ASM Diskgroup Utilization

Percentage

Max

10 minutes

Percentage of usable space used in a Disk Group. Usable space is the space available for growth. DATA disk group stores our Oracle database files. RECO disk group contains database files for recovery such as archives and flashback logs.

FilesystemUtilization

Filesystem Utilization

Percentage

Max

One minute

Percent utilization of provisioned filesystem.

CpuUtilization

CPU Utilization

Percentage

Mean

One minute

Percent CPU utilization.

MemoryUtilization

Memory Utilization

Percentage

Mean

One minute

Percentage of memory available for starting new applications, without swapping. The available memory can be obtained via the following command: cat /proc/meminfo.

SwapUtilization

Swap Utilization

Percentage

Mean

One minute

Percent utilization of total swap space.

LoadAverage

Load Average

Number

Mean

One minute

System load average over 5 minutes.

NodeStatus

Node Status

Integer

Mean

One minute

Indicates whether the host is reachable.

OcpusAllocated

OCPU Allocated

Integer

Max

One minute

The number of OCPUs allocated.

Using the API to Manage Exadata Cloud Infrastructure Instance

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.

Use these API operations to manage Exadata Cloud Infrastructure instance components.

Cloud Exadata infrastructure resource (new resource model):

Cloud VM cluster (new resource model)

DB systems (old resource model):

Virtual machines nodes (all Exadata Cloud Infrastructure instances):