Managing Bare Metal and Virtual Machine DB Systems

This topic explains how to perform a variety of management tasks for a bare metal or virtual machine database system. Tasks include:

  • Starting, stopping, rebooting, and terminating a DB system
  • Scaling the CPU count and storage
  • Managing network security groups (NSGs) for your system
  • Managing licenses for your DB system
  • Checking the system status
  • Moving a system to another compartment
  • Creating a serial console connection to your DB system nodes
  • Managing tags for your system
  • Viewing work requests related to your system
Warning

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.

Using the Console

To check the status of a DB system
  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of database 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 database systems and database nodes by using the ListDbSystems or ListDbNodes API operations, which return the lifecycleState attribute.

To start, stop, or reboot a database system

DB system nodes are stopped, started, or rebooted individually. For multi-node DB systems, you may need to act on only one node (as in the case of proactively rebooting a virtual machine node with scheduled maintenance).

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

    A list of database systems is displayed.

  3. In the list of database 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

    • Resource billing differs between bare metal and virtual machine DB systems as follows:

      • Bare metal DB systems - 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.
      • Virtual machine DB systems - Stopping a node stops billing for all OCPUs associated with that node. Billing resumes if you restart the node.
    • 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 the CPU cores for a bare metal DB system

If a bare metal DB system requires more compute node processing power, you can scale up (increase) the number of enabled CPU cores in the system without impacting the availability of that system.

Note

You cannot change the number of CPU cores for a virtual machine DB system in the same way. Instead, you must change the shape to one with a different number of OCPUs. See To change the shape of a virtual machine DB system to learn how.

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

    A list of database 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.
To change the shape of a virtual machine DB system

After you provision a virtual machine DB system, you can change the shape at any time to adapt to changes in performance needs. For example, you might require a system with a higher number of OCPUs, or you might want to reduce costs by reducing the number of OCPUs. See Virtual Machine DB Systems for resource details for each shape in a series.

Changing the shape does not impact the amount of storage available to the DB system. However, the new shape can have different memory and network bandwidth characteristics, and you might need to reapply any customizations to these aspects after the change.

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

    A list of database 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 Change Shape.
  5. Select the new shape from the list of compatible and available shapes, and click Change Shape. Compatible shapes are those shapes within the same series. For example, if the current shape is VM.Standard2.2, you can select another X7 shape that has not reached its usage limit in the selected availability domain.

    Note

    If the current shape supports Oracle RAC, then you can only change that shape to another shape that also supports Oracle RAC. For example, you cannot change the shape from VM.Standard2.2 to VM.Standard2.1.
  6. Review the information on the confirmation dialog, and proceed as applicable.

To scale up the storage for a virtual machine DB system

If a virtual machine DB system requires more block storage, you can increase the storage at any time without impacting the system.

Note

This procedure does not apply to bare metal DB systems.

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

    A list of database systems is displayed.

  3. In the list of DB systems, find the system you want to scale up and click its highlighted name.

    The system details are displayed.

  4. Click Scale Storage Up, and then select the new available storage size from the drop-down list.

    The new total storage size displays in the total storage field. Oracle charges for the total storage used.

  5. Click Update.

To move a 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 database 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 a 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 will be lost when the system is terminated. Oracle recommends that you back up any data in the DB system prior to terminating it.

Terminating a DB system removes all automatic incremental backups of all databases in the DB system from Oracle Cloud InfrastructureObject Storage. Full backups remain in Object Storage as standalone backups which you can use to create a new database. See Creating a Database for information on creating a new database from a backup.

Important: If your DB system has Data Guard enabled, you must terminate the standby DB system before terminating the primary DB system. If you try to terminate a primary DB system that has a standby, the terminate operation will not complete.

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

    A list of database 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 database system's icon indicates Terminating.

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

To edit the network security groups (NSGs) for your DB system

Your DB system can 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 DB Systems.

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

    A list of database 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 Network Security Groups field.
  5. In the Edit Network Security Groups dialog, click + Another Network Security Group to add an NSG to the DB system.

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

    To remove an NSG from your DB system, click the X icon to the right of the displayed NSG name.

  6. Click Save.
To manage your BYOL database licenses on your bare metal DB system

If you want to control the number of database licenses that you run at any given time on a bare metal system, 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 database 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 a bare metal or virtual machine DB system
  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 database 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 create a serial console connection to your database system
  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of database 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 Console Connections.
  5. Click Create Console Connection. Note that if all nodes currently have existing console connections, this button will be disabled.
  6. In the Create Console Connection dialog, specify the following:

    • The DB system node. For multi-node DB systems, select which node or nodes you wish to create a connection for. No node selector will display if the DB system has only one node, or if there is only one node in a multi-node system that currently lacks a connection.
    • The SSH key. You can browse or drag and drop .pub files, or paste in individual public keys.
  7. Click Create Console Connection.
To delete a serial console connection to your database system
  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of database 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 Console Connections. Your current console connections are displayed.
  5. To delete a connection, click the Actions icon (three dots) in the row listing the connection, then click Delete.

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 DB system components.

database systems:

Database homes:

Databases:

Nodes:

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