Managing an Exadata Cloud Service Instance

This topic describes management operations you can perform on an Exadata Cloud Service instance at the infrastructure level.

Note

If your instance uses the older DB system resource model, all of the management operations discussed in this topic take place on the DB system resource.

If your instance uses the newer Exadata Cloud Service instance resource model, most of the management operations discussed in this topic take place on the cloud VM cluster resource. However, some operations, including those related to infrastructure maintenance, take place on the cloud Exadata infrastructure resource.

For all of the management tasks, this topic states which resource types the operation takes place on.

You can perform the management tasks discussed in this topic by using the Oracle Cloud Infrastructure Console or the API.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  you should work in.

For administrators: The policy in Let database admins manage Oracle Cloud database 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.

Using the Console

To check the status of a cloud Exadata infrastructure resource
Note

This topic only applies to Exadata Cloud Service instances using the new Exadata Cloud Service instance resource model.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Click Exadata Infrastructure under Exadata at Oracle Cloud.
  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 resource:

    • 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 check the status of a cloud VM cluster
Note

This topic only applies to Exadata Cloud Service instances using the new Exadata Cloud Service instance resource model.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Click Exadata VM Clusters under Exadata at Oracle Cloud.
  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 Service instances using the DB system resource model.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Service cloud VM cluster or DB system
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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 the 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 scale CPU cores in an Exadata Cloud Service cloud VM cluster or DB system
Note

For information on adding additional database (compute) and storage servers to X8M 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 Service 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 3 cores per node.

CPU cores must be scaled symmetrically across all nodes in the cloud VM cluster or DB system. Use multiples of two for a base system or quarter rack, multiples of four for a half rack, and multiples of eight for a full rack. The total number of CPU cores in a rack must not exceed the maximum limit for that shape.

Tip

OCPU scaling activities are done online with no downtime.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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.

To move an Exadata Cloud Service 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 Service 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. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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 Exadata at Oracle Cloud, 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.

    For information about dependent resources for Database resources, see Moving Database Resources to a Different Compartment.

To terminate Exadata Cloud Service infrastructure-level resources

This topic describes how to terminate a cloud Exadata infrastructure, cloud VM cluster, or DB system resource in an Exadata Cloud Service 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 Service resource permanently deletes it and any databases running on it.

  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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 Exadata at Oracle Cloud, 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.

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 Service Instances.

  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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.
To manage your BYOL database licenses

If 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. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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 an Exadata Cloud Service 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. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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 Exadata at Oracle Cloud, 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.
To manage tags for your Exadata Cloud Service resources
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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.

For more information, see Resource Tags.

To view a work request for your Exadata Cloud Service resources
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  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.

For more information, see Work Requests.

To set the automatic maintenance schedule for Exadata Cloud Service infrastructure

This task describes how to set the maintenance schedule for a cloud Exadata infrastructure or Exadata DB system resource. See Oracle-Managed Infrastructure Maintenance Updates for more information on this type of maintenance.

  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Navigate to the cloud Exadata infrastructure or DB system you want to access:

    Cloud Exadata infrastructure (new resource model): Under Exadata at Oracle Cloud, 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.

    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.

  3. On the resource details page, under Maintenance or Infrastructure Maintenance, click the edit link in the Maintenance Schedule field.
  4. In the Automatic Maintenance Schedule dialog, select Specify a schedule.
  5. Under Maintenance months, specify at least one month for each quarter during which Exadata infrastructure maintenance will take place. You can select more than one month per quarter. If you specify a long lead time for advanced notification (for example, 4 weeks), then you may want to specify two or three months per quarter during which maintenance runs can occur. This will ensure that your maintenance updates are applied in a timely manner after accounting for your required lead time. Lead time is discussed in the following steps.

  6. Under Week of the month, specify which week of the month maintenance will take place. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of seven days. Weeks start and end based on calendar dates, not days of the week. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days.

  7. Optional. Under Day of the week, specify the day of the week on which the maintenance will occur. If you do not specify a day of the week, then Oracle will run the maintenance update on a weekend day to minimize disruption.

  8. Optional. Under Start hour, specify the hour during which the maintenance run will begin. If you do not specify a start hour, then Oracle will choose the least disruptive time to run the maintenance update.

  9. Under Lead Time, specify the number of weeks ahead of the maintenance event you would like to receive a notification message. Your lead time ensures that a newly released maintenance update is scheduled to account for your required period of advanced notification.

  10. Click Update Maintenance Schedule.
To view or edit the time of the next scheduled maintenance for Exadata Cloud Service infrastructure
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Navigate to the cloud Exadata infrastructure or DB system you want to access:

    Cloud Exadata infrastructure (new resource model): Under Exadata at Oracle Cloud, 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.

    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.

  3. On the resource details page, under Maintenance or Infrastructure Maintenance, click the view link in the Next Maintenance field.
  4. On the Maintenance page, scheduled maintenance events are listed.
  5. Optional. To change the time of the next scheduled maintenance, click the Edit link in the Scheduled Start Time field.
  6. In the Edit Infrastructure Maintenance Scheduled Start Time dialog, enter a date and time in the Scheduled start time field. 

    The following restrictions apply: 

    • Infrastructure maintenance cannot be rescheduled to occur more than six months after the announcement of the maintenance update's availability. If a new patch is announced prior to your rescheduled maintenance run, the newer patch will be applied on your specified date. You can reschedule your maintenance to take placer earlier than it is currently scheduled.
    • Oracle reserves certain dates each quarter for internal maintenance operations, and you cannot schedule your maintenance on these dates. When using the Console, the selection of these dates is disabled.
  7. Click Update Scheduled Start Time.
To view the maintenance history of an Exadata Cloud Service infrastructure resource

This task describes how to view the maintenance history for a cloud Exadata infrastructure or DB system. resource. See Oracle-Managed Infrastructure Maintenance Updates for more information on this type of maintenance.

  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Navigate to the cloud Exadata infrastructure or DB system you want to access:

    Cloud Exadata infrastructure (new resource model): Under Exadata at Oracle Cloud, 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.

    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.

  3. On the resource details page, under Maintenance or Infrastructure Maintenance, click the view link in the Next Maintenance field.
  4. Click Maintenance History to see a list of past maintenance events including details on their completion state.

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 Service instance components.

DB systems (old resource model):

Nodes: