Managing VM Clusters on Exadata Cloud at Customer

This topic explains how to manage virtual machine (VM) clusters on Exadata Cloud at Customer.

Before you can create any databases on your Exadata Cloud at Customer infrastructure, you must create a VM cluster network and associate it with a VM cluster. Each Exadata Cloud at Customer infrastructure can support one VM cluster network and associated VM cluster.

The VM cluster network specifies network resources, such as IP addresses and host names, that reside in your corporate data center and are allocated to Exadata Cloud at Customer. The VM cluster network includes definitions for the Exadata client network and the Exadata backup network. The client network and backup network contain the network interfaces that you use to connect to the VM cluster compute nodes, and ultimately the databases that reside on those compute nodes.

The VM cluster provides a link between your Exadata Cloud at Customer infrastructure and databases. The VM cluster contains an installation of Oracle Clusterware, which supports the databases in the cluster. In the VM cluster definition, you also specify the number of enabled CPU cores, which determines the amount of CPU resources that are available to your databases.


Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

For administrators: The policy in Let database admins manage DB systems lets the specified group do everything with databases and related Database resources.

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for databases, see Details for the Database Service.


The public key, in OpenSSH format, from the key pair that you plan to use for connecting to the VM cluster compute nodes via SSH. The following shows a sample public key, which is abbreviated for readability.

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAA....lo/gKMLVM2xzc1xJr/Hc26biw3TXWGEakrK1OQ== rsa-key-20160304

For more information, see Managing Key Pairs on Linux Instances

Using the Console

To create a VM cluster network
To edit a VM cluster network
To download a file containing the VM cluster network configuration details
To validate a VM cluster network
To terminate a VM cluster network
To create a VM cluster
To scale the CPU resources on a VM cluster
To stop, start, or reboot a VM cluster compute node
To check the status of a VM cluster compute node
To update the license type on a VM cluster
To move a VM cluster to another compartment
To terminate a VM cluster

Using the API

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 at Customer VM cluster networks and VM clusters:

VM cluster networks:

VM clusters:

For the complete list of APIs, see Database Service API.