Oracle Cloud Infrastructure Documentation

Manage Exadata Cloud Infrastructure

Use the provided tools to manage the Infrastructure.

Using the Console to Provision Exadata Cloud Infrastructure

Learn how to provision an Exadata Cloud Infrastructure system.

Lifecycle Management Operations

To check the status of a Cloud Exadata infrastructure resource
Note

This topic only applies to Exadata Cloud Infrastructure instances using the new Exadata Cloud Infrastructure instance resource model.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Click Exadata Infrastructure under Oracle Exadata Database Service on Dedicated Infrastructure.

  4. In the list of Cloud Exadata infrastructure resources, click the name of the infrastructure you're interested in and check its icon. The icon text indicates the status of the system. The following lifecycle states apply to the Cloud Exadata infrastructure

    • Provisioning: Reources are being reserved for the Cloud Exadata infrastructure resource. Provisioning can take several minutes. The resource is not ready to be used.
    • Available: The Cloud Exadata infrastructure was successfully provisioned. You can create a cloud VM cluster on the resource to complete the infrastructure provisioning.
    • Updating: The Cloud Exadata infrastructure is being updated. The resource goes into the updating state during management tasks. For example, when moving the resource to another compartment, or creating a cloud VM cluster on the resource.
    • Maintenance in Progress: A maintenance update is currently being performed on the infrastructure resource. See Maintaining an Exadata Cloud Service Instance for details on infrastructure maintenance scheduling and impacts.
    • Terminating: The Cloud Exadata infrastructure is being deleted by the terminate action in the Console or API.
    • Terminated:The Cloud Exadata infrastructure has been deleted and is no longer available.
    • Failed: An error condition prevented the provisioning or continued operation of the Cloud Exadata infrastructure.
To change the infrastructure display name
Note

This topic only applies to Exadata Cloud Infrastructure instances using the new Exadata Cloud Service instance resource model.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Click Exadata Infrastructure under Oracle Exadata Database Service on Dedicated Infrastructure.

  4. In the list of Cloud Exadata infrastructure resources, click the name of the infrastructure you're interested in

  5. On rthe Infrastructure Details page, click Update Display Name .
  6. In the Update Display Name dialog, Enter the New display name, and the current display name as instructed.
  7. Click Update Display Name.
To check the status of a cloud VM cluster
Note

This topic only applies to Exadata Cloud Infrastructure instances using the new Exadata Cloud Infrastructure instance resource model.
  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 under Oracle Exadata Database Service on Dedicated Infrastructure.

  4. In the list of cloud VM clusters, find the cluster you're interested in and check its icon. The icon text indicates the status of the system. The following lifecycle states apply to the cloud VM cluster:

    • Provisioning: Resources are being reserved for the Cloud Exadata infrastructure resource. Provisioning can take several minutes. The resource is not ready to use yet.
    • Available: The Cloud Exadata infrastructure was successfully provisioned. You can create a cloud VM cluster on the resource to complete the infrastructure provisioning.
    • Updating: The Cloud Exadata infrastructure is being updated. The resource goes into the updating state during management tasks. For example, when moving the resource to another compartment, or creating a cloud VM cluster on the resource.
    • Terminating: The Cloud Exadata infrastructure is being deleted by the terminate action in the Console or API.
    • Terminated:The Cloud Exadata infrastructure has been deleted and is no longer available.
    • Failed: An error condition prevented the provisioning or continued operation of the Cloud Exadata infrastructure.

    To view the status of a virtual machine (database node) in the cloud VM cluster, under Resources, click Virtual Machines to see the list of virtual machines. In addition to the states listed for a cloud VM cluster, a virtual machine's status can be one of the following:

    • Starting: The database node is being powered on by the start or reboot action in the Console or API.
    • Stopping: The database node is being powered off by the stop or reboot action in the Console or API.
    • Stopped: The database node was powered off by the stop action in the Console or API.
To check the status of an Exadata DB system
Note

This topic only applies to Exadata Cloud Infrastructure instances using the DB system resource model.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure

  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. In the list of DB systems, find the system you're interested in and check its icon. The icon text indicates the status of the system. The following lifecycle states apply to the DB system resource:

    • Provisioning: Resources are being reserved for the DB system, the system is booting, and the initial database is being created. Provisioning can take several minutes. The system is not ready to use yet.
    • Available: The DB system was successfully provisioned. A few minutes after the system enters this state, you can SSH to it and begin using it.
    • Terminating: The DB system is being deleted by the terminate action in the Console or API.
    • Terminated: The DB system has been deleted and is no longer available.
    • Failed: An error condition prevented the provisioning or continued operation of the DB system.

    To view the status of a database node, under Resources, click Nodes to see the list of nodes. In addition to the states listed for a DB system, a node's status can be one of the following:

    • Starting: The database node is being powered on by the start or reboot action in the Console or API.
    • Stopping: The database node is being powered off by the stop or reboot action in the Console or API.
    • Stopped: The database node was powered off by the stop action in the Console or API.

You can also check the status of DB systems and database nodes using the ListDbSystems or ListDbNodes API operations, which return the lifecycleState attribute.

To start, stop, or reboot an Exadata Cloud Infrastructure cloud VM cluster or DB system
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.

  3. Navigate to the cloud VM cluster or DB system you want to start, stop, or reboot:

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. Under Resources, click Virtual Machines (for cloud VM clusters) or Nodes (for DB systems) to display the compute nodes of the cloud service instance. Click Actions icon (three dots) for a node and then click one of the following actions:

    • Start:;Restarts a stopped node. After the node is restarted, the Stop action is enabled.
    • Stop: Shuts down the node. After the node is powered off, the Start action is enabled.
    • Reboot: Shuts down the node, and then restarts it.
    Note

    • For billing purposes, the Stop state has no effect on the resources you consume. Billing continues for virtual machines or nodes that you stop, and related resources continue to apply against any relevant quotas. You must Terminate a cloud VM cluster or DB system to remove its resources from billing and quotas.
    • After you restart or reboot a node, the floating IP address might take several minutes to be updated and display in the Console.
To terminate Exadata Cloud Infrastructure infrastructure-level resources

This topic describes how to terminate a Cloud Exadata infrastructure, cloud VM cluster, or DB system resource in anExadata Cloud Infrastructure instance.

Note

The database data is local to the cloud VM cluster or DB system hosting it and is lost when the system is terminated. Oracle recommends that you back up any data in the cloud VM cluster or DB system before terminating it.

Terminating an Exadata Cloud Infrastructure resource permanently deletes it and any databases running on it. The data is deleted in compliance with the NIST SP-800-88r1 standard and implemented as an Exadata crypto erase using the hardware Instant Secure Erase (ISE) feature of the Exadata storage devices, as documented in the Exadata Database Machine Documentation at Securely Erasing Exadata Database Machine

  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose your Compartment.

  3. Navigate to the Cloud Exadata infrastructure, cloud VM cluster or DB system you want to move:

    Cloud Exadata infrastructure (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata Infrastructure. In the list of infrastructure resources, find the infrastructure you want to access and click its highlighted name to view its details page.

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. For cloud VM clusters and DB systems, click More Actions, then Terminate on the resource details page. For Cloud Exadata infrastructure resources, click Terminate on the resource details page.

    Confirm when prompted.

    The resource's icon indicates Terminating.

    Note

    If you are terminating a Cloud Exadata infrastructure resource that contains a cloud VM cluster, you must check the box labelled Also delete the VM cluster associated with this infrastructure to confirm that you intend to delete the VM cluster.

At this point, you cannot connect to the system and any open connections are terminated.

Using the Console to View a List of DB Servers on an Exadata Infrastructure

To view a list of database server hosts on an Oracle Exadata Database Service on Dedicated Infrastructure system, use this procedure.

  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 Infrastructure.
  3. In the list of Exadata Infrastructures, click the display name of the infrastructure you wish to view details.
  4. Under Resources, click DB Servers.
  5. In the list of DB Servers, click the name of the DB Server that you wish to view details.

    DB Server lists VMs from each cluster hosted on them along with resources allocated to them.

Network Management Operations

To edit the network security groups (NSGs) for your client or backup network

Your client and backup networks can each use up to five network security groups (NSGs). Note that if you choose a subnet with a security list, the security rules for the cloud VM cluster or DB system will be a union of the rules in the security list and the NSGs. For more information, see Network Security Groups and Network Setup for Exadata Cloud Infrastructure Instances.

  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Navigate to the cloud VM cluster or DB system you want to manage:

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. In the Network details, click the Edit link to the right of the Client Network Security Groups or Backup Network Security Groups field.

  5. In the Edit Network Security Groups dialog, click + Another Network Security Group to add an NSG to the network.

    To change an assigned NSG, click the drop-down menu displaying the NSG name, then select a different NSG.

    To remove an NSG from the network, click the X;icon to the right of the displayed NSG name.

  6. Click Save.

Management Tasks for the Oracle Cloud Infrastructure Platform

To view a work request for your Exadata Cloud Infrastructure resources
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure.

  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. Find the Cloud Exadata infrastructure, cloud VM cluster, DB system or database resource you're interested in, and click the name.
  4. In the Resources section, click Work Requests. The status of all work requests appears on the page.

  5. To see the log messages, error messages, and resources that are associated with a specific work request, click the operation name. Then, select an option in the More information section.

    For associated resources, you can click the Actions icon (three dots) next to a resource to copy the resource's OCID.

To move an Exadata Cloud Infrastructure resource to another compartment
Note

  • To move resources between compartments, resource users must have sufficient access permissions on the compartment that the resource is being moved to, as well as the current compartment. For more information about permissions for Database resources, see Details for the Database Service.
  • If your Exadata Cloud Infrastructure instance is in a security zone, the destination compartment must also be in a security zone. See the Security Zone Policies topic for a full list of policies that affect Database service resources.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. Choose your Compartment.

  3. Navigate to the Cloud Exadata infrastructure, cloud VM cluster or DB system you want to move:

    Cloud Exadata infrastructure (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata Infrastructure. In the list of infrastructure resources, find the infrastructure you want to access and click its highlighted name to view its details page.

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.
  4. Click Move Resource.
  5. Select the new compartment.
  6. Click Move Resource.
To manage tags for your Exadata Cloud Infrastructure resources
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Find the Cloud Exadata infrastructure, cloud VM cluster, DB system or database resource you're interested in, and click the name.
  4. Click the Tags tab to view or edit the existing tags. Or click More Actions and then Apply Tags to add new ones.
Managing Infrastructure Maintenance Contacts

Learn to manage your Exadata infrastructure maintenance contacts.

Parent topic: Management Tasks for the Oracle Cloud Infrastructure Platform

To manage maintenance contacts in an Exadata Cloud Infrastructure

Manage contacts for Exadata infrastructure maintenance notifications using the Console.

To prevent an Exadata infrastructure administrator from being overwhelmed by system update notifications, you can specify up to 10 email addresses of people to whom maintenance notifications are sent.

  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure.
  2. In the Oracle Exadata Database Service on Dedicated Infrastructure section, click Exadata Infrastructure to display a list of Exadata infrastructures in the default compartment. You can select a different compartment from the Compartment drop-down located in the List Scope section.
  3. In the list of Exadata infrastructure resources, find the infrastructure you want to access and click its highlighted name to view its details page.
  4. In the Maintenance section, click Manage in the Customer Contacts field to display the Manage Contacts dialog.
  5. Click the Add Contacts button to display a field in which to enter a valid email address. You can have up to 10 maintenance contacts for each Exadata infrastructure.
  6. To edit an email address, in the Manage Contacts dialog, select the box preceding the email address you want to edit and click the Edit button.
  7. To remove an email address from the list, in the Manage Contacts dialog, select the box preceding the email address you want to remove and click the Remove button.

Oracle Database License Management Tasks

Parent topic: Using the Console to Provision Exadata Cloud Infrastructure

To manage your BYOL database licenses

f you want to control the number of database licenses that you run at any given time, you can scale up or down the number of OCPUs on the instance. These additional licenses are metered separately.

  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.

  3. Navigate to the cloud VM cluster or DB system you want to scale:

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. Click Scale VM Cluster (for cloud VM clusters) or Scale CPU;Cores (for DB systems) and then specify a new number of CPU cores. The text below the field indicates the acceptable values, based on the shape used when the DB system was launched.
  5. Click Update.
To change the license type of a cloud VM cluster or DB system
Note

Updating the license type is not supported for systems running on the X6 shape. The feature is supported for X7 and higher shapes.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.

  3. Navigate to the cloud VM cluster or DB system you want to manage:

    1. Cloud VM clusters ( new resource model) Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

      DB systems Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. On the resource details page, click Update License Type.

    The dialog displays the options with your current license type selected.

  5. Select the new license type.
  6. Click Save.

Scaling Resources within an Exadata Infrastructure Instance

If an Exadata Cloud Infrastructure instance requires more resources, you can scale up the number of DB servers, or storage servers.

There are three distinct scaling paths:
  • Scaling an X8M or X9M based Multi-VM enabled Infrastructure by adding DB servers and Storage servers to an existing infrastructure. See Add Resources To a Multi-VM Enabled Infrastructure
  • Scaling an X8M or X9M based that is NOT a Multi-VM enabled Infrastructure. See Scaling Exadata X8M and X9M Compute and Storage
  • Scaling an X6, X7 and X8 Exadata infrastructure (fixed shape). See Scaling X6, X7 and X8 Exadata DB System Configurations

Related Topics

Parent topic: Using the Console to Provision Exadata Cloud Infrastructure

Add Resources to a Multi-VM enabled Infrastructure

Add DB servers or storage servers to an existing Multi-VM enabled Infrastructure

You can scale an X8M or X9M Exadata Multi-VM enabled Infrastructure instance in the Console on the cloud Exadata infrastructure details page. After adding additional database or storage servers to your cloud Exadata infrastructure resource, you must add the increased capacity to the associated cloud VM cluster to utilize the newly-provisioned CPU or storage resources.

Adding DB servers, or Storage servers do not require any database downtime.

Note

  • Neither the Exadata X8M nor the X9M shapes support removing storage or database servers from an existing cloud infrastructure instance.

To add DB Servers to Multi-VM enabled Infrastructure

  1. Navigate to Oracle Cloud menu and click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Select Exadata Infrasrtucture under Oracle Exadata Database Service on Dedicated Infrastructure
  3. Select the desired Infrastructure in the desired compartment.
  4. On the Infrastructure Details page click Scale Infrastructure.
  5. In the Scale Infrastructure page, set the Additional DB servers to a value so that the total of DB servers is 8 or less.
  6. Click Scale Infrastructure.

To add storage servers to Multi-VM enabled Infrastructure

  1. Navigate to Oracle Cloud menu and click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Select Exadata Infrastructure under Oracle Exadata Database Service on Dedicated Infrastructure
  3. Select the desired Infrastructure in the desired compartment.
  4. On the Infrastructure Details page click Scale Infrastructure.
  5. In the Scale Infrastructure page, set the Additional storage servers to a value so that the total of storage servers is 12 or less.
    Note

    • This operation adds the storage servers to the infrastructure, but the storage capacity must be made available for VM Cluster consumption.
    • You will be able to scale down a storage server if the server has not been used to expand Exadata infrastructure storage.
  6. Click Scale Infrastructure.
  7. On the Infrastructure Details page, a banner directs you to Add Storage Cappacity to make the the storage capacity available for VM Cluster consumption.
  8. Click Add Storage Capacity.
  9. In the Add Storage Capacity page, click Add Storage Capacity.
Remove DB Servers from a Multi-VM enabled Infrastructure

Remove DB servers from an existing Multi-VM enabled Infrastructure

  • Database servers will be removed if there are no VMs running on them.
    Note

    You will not be able to choose the DB Server to remove. This functionality will automatically remove Database Servers in which there are no VMs.

For more information about removing a VM, see Terminate a VM from a VM Cluster.

Scaling CPU cores within an Exadata Cloud Infrastructure instance

If an Exadata Cloud Infrastructure instance requires more compute node processing power, you can scale up the number of enabled CPU cores symmetrically across all the nodes in the system as follows:

The options for each of the shapes are:

X8M or X9M flexible infrastructure systems: You can scale CPU cores in multiples of the number of database servers currently provisioned for the cloud VM cluster. For example, if you have 6 database servers provisioned, you can add CPU cores in multiples of 6. At the time of provisioning, X8M systems have as few as 2 database servers or up to 32 database servers.. For more information on adding compute and storage resources to an X8M or X9M system, see Scaling Exadata X8M and X9M Compute and Storage .

Non-X8M fixed-shape systems: For a base system or an X7 or X8 quarter rack, you can scale in multiples of 2 across the 2 database compute nodes. For an X7 or X8 half rack, you can scale in multiples of 4 across the 4 database compute nodes. For an X7 or X8 full rack, you can scale in multiples of 8 across the 8 database compute nodes.

For a non-metered service instances, you can temporarily modify the compute node processing power (bursting) or add compute node processing power on a more permanent basis. For a metered service instance, you can simply modify the number of enabled CPU cores.

You can provision an Exadata Cloud Infrastructure instance with zero CPU cores, or scale the service instance down to zero cores after you provision it. With zero cores, you are billed only for the infrastructure until you scale up the system. For detailed information about pricing, see Exadata Cloud Service Pricing.

Note

OCPU scaling activities are done online with no downtime.

For information on CPU cores per configuration, see Exadata Shape Configurations. To learn how to scale a system, see To scale CPU cores in an Exadata Cloud Infrastructure cloud VM cluster or DB system .

Related Topics

Parent topic: Scaling Resources within an Exadata Infrastructure Instance

Scaling Exadata X8M and X9M Compute and Storage

The flexible X8M and X9M system model is designed to be easily scaled in place, with no need to migrate the database using a backup or Data Guard

You can scale an X8M or X9M Exadata cloud infrastructure instance in the Console on the cloud Exadata infrastructure details page. After adding additional database or storage servers to your cloud Exadata infrastructure resource, you must add the increased capacity to the associated cloud VM cluster to utilize the newly-provisioned CPU or storage resources. After adding additional database servers to a VM cluster, you can then allocate the new CPU cores as described in see To scale CPU cores in an Exadata Cloud Infrastructure cloud VM cluster or DB system. After adding additional storage servers to your VM cluster, you do not need to take any further action to utilize the new storage.

Note

  • Neither the Exadata X8M nor the X9M shapes support removing storage or database servers from an existing cloud infrastructure instance.
To add compute and storage resources to a flexible cloud Exadata infrastructure resource

This task describes how to use the Oracle Cloud Infrastructure Console to scale a flexible cloud Exadata infrastructure resource.

Currently, only Exadata X8M and X9M systems in Oracle Cloud Infrastructure have the ability to add database (compute) and storage servers to an existing service instance.

  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 Infrastructure.
  3. In the list of cloud Exadata infrastructure resources, click the name of the resource you want to scale.
  4. Click Scale Infrastructure.
  5. Add either Database servers or Storage Servers by selecting the proper radio button
    1. Adding database servers: To add compute servers to the infrastructure resource, select the Database Servers radio button, then enter the number of servers you want to add in the Database servers field.
    2. Adding storage servers: To add storage servers to the infrastructure resource, select the Storage Servers radio button, then enter the number of servers you want to add in the Storage servers field.
  6. Click Scale.
Note

After scaling your infrastructure, you must add the new capacity to the cloud VM cluster before you can use the additional CPU and storage resources in the Exadata Cloud Infrastructure instance.

To scale CPU cores in an Exadata Cloud Infrastructure cloud VM cluster or DB system
Note

For information on adding additional database (compute) and storage servers to X8M or X9M cloud VM clusters, see To add compute and storage resources to a flexible cloud Exadata infrastructure resource and To add database server or storage server capacity to a cloud VM cluster. Adding additional database servers to your X8M cloud VM cluster will increase the number of CPU cores available for scaling.

If an Exadata Cloud Infrastructure instance requires more compute node processing power, you can scale up (increase) the number of enabled CPU cores (OCPUs) in the instance.

You can also scale a cloud VM cluster or DB system (except for X6 systems) down to zero (0) CPU cores to temporarily stop the system and be charged only for the hardware infrastructure. For more information about scaling down, see Scaling Options. Oracle recommends that if you are not scaling down to a stopped system (0 cores), that you scale to at least 2 cores per node.
Note

The minimum cores is 1 for X8 and older, minimum for X8M and newer is 2.

CPU cores must be scaled symmetrically across all nodes in the cloud VM cluster or DB system. Use multiples of two CPUs per database server. For example, if you have two database servers, a minimum of 2 CPU cores per server or a total of 4 CPU cores. The total number of CPU cores must not exceed the maximum limit for that shape and/or resources.

Tip:

OCPU scaling activities are done online with no downtime.
  1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure
  2. Choose your Compartment.
  3. Navigate to the cloud VM cluster or DB system you want to scale:

    Cloud VM clusters (new resource model): Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. Click Scale VM Cluster (for cloud VM clusters) or Scale CPU;Cores (for DB systems) and then specify a new number of CPU cores. The text below the field indicates the acceptable values, based on the shape used when the DB system was launched.

  5. Click Update.

Note

If you scale an scale a cloud VM cluster or DB system (except for X6 systems) down to zero (0) CPU cores, the floating IP address of the nodes might take several minutes to be updated and display in the Console.
Scaling X6, X7 and X8 Exadata DB System Configurations

Scaling an Exadata X6, X7, or X8 Exadata Cloud Infrastructure instance by moving to a shape with more capacity enables you meet the needs of your growing workload.

This is useful when a database deployment requires:

  • Processing power that is beyond the capacity of the current system configuration.
  • Storage capacity that is beyond the capacity of the current system configuration.
  • A performance boost that can be delivered by increasing the number of available compute nodes.
  • A performance boost that can be delivered by increasing the number of available Exadata Storage Servers.

You can move you workloads to a larger fixed shape (X7 and X8 hardware shapes), or move to the flexible X8M shape that allows for easy expansion of compute and storage resources as your workloads grow.

To assist with moving your database deployments between Exadata Cloud Infrastructuree instances, you can restore a backup to a different service instance that has more capacity, or create a Data Guard association for your database in a service instance with more capacity, and then perform a switchover so that your new standby database assumes the primary role. To start the process, contact Oracle and request a service limit increase so that you can provision the larger service instance needed by your database.

Using the API to Create Infrastructure Components

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 create Exadata Cloud Infrastructure components.

APIs for the New Exadata Cloud Infrastructure Resource Model

The new Exadata resource model is compatible with all offered Exadata shape families (X7, X8, and X8M). See The Exadata Cloud Infrastructure Resource Model for more information.

Tip:

As of November 15, 2021 new Exadata Cloud Infrastructure instances may only be provisioned using the new resource model.

Cloud Exadata infrastructure resource:

Cloud VM cluster resource:

Databases

Shapes and Database Versions

Database Homes

Note

The DB system APIs are deprecated forExadata Cloud Infrastructure. Oracle recommends converting existing Exadata DB systems to the new resource model as soon as possible. Converting to the new resource model does not involve system downtime. Learn more.

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):