Oracle Cloud Infrastructure Documentation

Managing Bare Metal and Virtual Machine DB Systems

This topic explains how to launch, start, stop, terminate, scale, manage licenses for, and check the status of a bare metal and virtual machine DB system, and set up DNS for a 1-node or 2-node RAC DB system.

When you launch a DB system using the Console, the API, or the CLI, the system is provisioned to support Oracle databases and an initial database is created based on the options you provide and some default options described later in this topic.


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 An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. 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 A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in.

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


You'll need the following items to launch any DB system.

  • The public key, in OpenSSH format, from the key pair that you plan to use for connecting to the DB System via SSH. A sample public key, abbreviated for readability, is shown below.

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

    For more information, see Managing Key Pairs on Linux Instances

  • The name of a virtual cloud network (VCN)  to launch the DB System in. For information about setting up cloud networks, see Overview of Networking. See the additional requirements below.
  • Do not use a subnet that overlaps with, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet will cause the private interconnect to malfunction.
  • For a 2-node RAC DB system, the subnet must have at least six available IP addresses. Three of each subnet's IP addresses are reserved, so the minimum allowed subnet size is /28. For more information, see Allowed VCN Size and Address Ranges.
  • If you plan to back up your DB system to Object Storage or to use the managed patching feature, you can use a service gateway with a private subnet or an internet gateway with a public subnet. For information about service gateways, see Access to Object Storage: Service Gateway. For details about these networking options, see Connectivity Choices.


    • With an internet gateway, network traffic between the system and Object Storage does not leave the cloud and never reaches the public internet. For more information, see Internet Gateway.
    • See Known Issues for information about OS updates when using a service gateway.
  • Each VCN subnet has a default security list that contains a rule to allow TCP traffic on destination port 22 (SSH) from source and any source port. You can update the default security list or create new lists to allow other types of access, but this can be done before or after you launch the DB system. For more information, see Security Lists.
  • For a 2-node RAC DB system, ensure that port 22 is open for both ingress and egress on the subnet, and that the security rules you create are stateful (the default), otherwise, the DB system might fail to provision successfully.
  • If you need DNS name resolution for the system, decide whether to use a Custom Resolver (your choice of DNS server) or the Internet and VCN Resolver (the DNS capability built in to the VCN). For more information, see DNS in Your Virtual Cloud Network.

Default Options for the Initial Database

To simplify launching a DB system in the Console and when using the API, the following default options are used for the initial database and for any additional databases that you create. (Several advanced options such as Time Zone can be set when you can use the dbcli command line interface to create databases.)

  • Console Enabled: False
  • Create Container Database: False for version databases. Otherwise, true.
  • Create Instance Only (for standby and migration): False
  • Database Home ID: Creates a new database home
  • Database Language: AMERICAN
  • Database Sizing Template: odb2
  • Database Storage: ACFS for version databases. Otherwise, ASM.
  • Database Territory: AMERICA
  • Database Unique Name: The user-specified database name and a system-generated suffix, for example, dbtst_phx1cs.
  • PDB Admin Name: pdbuser (Not applicable for version databases.)

For a list of the database options that you can set, see To launch a DB system.

Using the Console

To launch a DB system
To check the status of a DB system
To start, stop, or reboot a DB system
To scale the CPU cores for a bare metal DB system
To scale up the storage for a virtual machine DB system
To terminate a DB system
To manage your BYOL database licenses
To manage tags for your DB systems and database resources

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.

DB systems:

Database homes:



Shapes and database versions:

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

Setting up DNS for a DB System

DNS lets you use host names instead of IP addresses to communicate with a DB system. You can use the Internet and VCN Resolver (the DNS capability built into the VCN) as described in DNS in Your Virtual Cloud Network.

Alternatively, you can use your choice of DNS server. You associate the host name and domain name to the public or private IP address of the DB system. You can find the host and domain names and IP addresses for the DB system in the Oracle Cloud Infrastructure Console on the Database page.

To associate the host name to the DB system's public or private IP address, contact your DNS administrator and request a custom DNS record for the DB system’s IP address. For example, if your domain is and you want to use clouddb1 as the host name, you would request a DNS record that associates to your DB system's IP address.

If you provide the public IP address to your DNS administrator as described above, you should also associate a custom domain name to the DB system's public IP address:

  1. Register your domain name through a third-party domain registration vendor, such as
  2. Resolve your domain name to the DB system's public IP address, using the third-party domain registration vendor console. For more information, refer to the third-party domain registration documentation.