Managing Exadata DB Systems

You can start, stop, terminate, scale, manage licenses for, and check the status of, an Exadata DB system by using the Oracle Cloud Infrastructure Console or the API.

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.

Using the Console

To check the status of an Exadata DB system
  1. Open the navigation menu. Under 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 color of the icon and the text next to it indicates the status of the system.

    • Provisioning: Yellow icon. 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: Green icon. 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: Gray icon. The DB system is being deleted by the terminate action in the Console or API.
    • Terminated: Gray icon. The DB system has been deleted and is no longer available.
    • Failed: Red icon. 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: Yellow icon. The database node is being powered on by the start or reboot action in the Console or API.
    • Stopping: Yellow icon. The database node is being powered off by the stop or reboot action in the Console or API.
    • Stopped: Yellow icon. 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 DB system
  1. Open the navigation menu. Under 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 DB system you want to stop or start, and then click its name to display details about it.
  4. In the list of nodes, 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 nodes that you stop, and related resources continue to apply against any relevant quotas. You must Terminate a 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 an Exadata DB system

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

You can also scale an X8 or X7 Exadata DB system, or an Exadata base system, 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 an Exadata DB System. 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 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 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 want to scale and click its highlighted name.

    The system details are displayed.

  4. Click Scale CPU Cores and then change the number in the CPU Core Count field. 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 X8 or X7 Exadata DB system, or an Exadata base system, 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 DB system 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.
  1. Open the navigation menu. Under 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 want to move and click its highlighted name.

    The system details are displayed.

  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 an Exadata DB system

Terminating a DB system permanently deletes it and any databases running on it.

Note

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

  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. For the DB system you want to terminate, click the Actions icon (three dots), and then click Terminate.
  4. Confirm when prompted.

    The DB system's icon indicates Terminating.

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 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 DB Systems.

  1. Open the navigation menu. Under 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 want to manage and click its highlighted name.

    The system details are displayed.

  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 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 want to scale and click its highlighted name.

    The system details are displayed.

  4. Click Scale CPU Cores, and then change the number.
To change the license type of an Exadata 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 Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. In the list of DB systems, find the DB system you want to administer and click its highlighted name.
  4. On the DB system 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.
See Known Issue.
To manage tags for your DB systems and database resources
  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Find the 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 DB systems and database resources
  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. Find the 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 DB system infrastructure

This task describes how to set the maintenance schedule for an Exadata DB system's infrastructure. See Oracle Managed Infrastructure Maintenance Updates for more information on this type of maintenance.

  1. Open the navigation menu. Under 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 want to set the maintenance window for and click its highlighted name.

    The system details are displayed.

  4. On the DB system details page, under Maintenance, click the edit link in the Maintenance Schedule field.
  5. In the Automatic Maintenance Schedule dialog, select Specify a schedule.
  6. 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), you may wish to specify 2 or 3 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.
  7. 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 7 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.
  8. 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, Oracle will run the maintenance update on a weekend day to minimize disruption.
  9. Optional. Under Start hour, specify the hour during which the maintenance run will begin. If you do not specify a start hour, Oracle will pick the least disruptive time to run the maintenance update.
  10. 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.
  11. Update Maintenance Schedule.
To view or edit the time of the next scheduled maintenance for Exadata DB system infrastructure
  1. Open the navigation menu. Under 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 want to set the maintenance window for and click its highlighted name.

    The system details are displayed.

  4. On the DB system details page, under Maintenance, click the view link in the Next Maintenance field.
  5. On the Maintenance page, scheduled maintenance events are listed.
  6. Optional. To change the time of the next scheduled maintenance, click the Edit link in the Scheduled Start Time field.
  7. 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.
To view the maintenance history of Exadata DB system infrastructure

This task describes how to view the maintenance history for an Exadata DB system's infrastructure. See Oracle Managed Infrastructure Maintenance Updates for more information on this type of maintenance.

  1. Open the navigation menu. Under 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 want to set the maintenance window for and click its highlighted name.

    The system details are displayed.

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