Creating Bare Metal and Virtual Machine DB Systems

This topic explains how to create a bare metal or virtual machine DB system, and set up DNS for a single-node or two-node Oracle RAC DB system.

When you create 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 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. For more information about writing policies for databases, see Details for the Database Service.


You'll need the following items to create 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

  • A correctly configured virtual cloud network (VCN) to launch the DB system in. Its related networking resources (gateways, route tables, security lists, DNS, and so on) must also be configured as necessary for the DB system. For more information, see Network Setup for DB Systems.
  • If you plan to back up your DB system to Object Storage or to use the managed patching feature, then Oracle recommends using a service gateway to enable access to Object Storage. For more information, see Service Gateway for the VCN.
  • For a two-node Oracle 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.

Default Options for the Initial Database

To simplify creating 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 Oracle Database 11g ( 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 Oracle Database 11g ( databases. Otherwise, ASM for all bare metal and multi-node virtual machine DB systems. Single-node VM systems can optionally be provisioned using Logical Volume Manager for faster provisioning.
  • 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 Oracle Database 11g ( databases.)

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

Using a Backup to Create the Initial Database

When creating a new DB system using a backup stored in Object Storage as the source of the initial database, you have the following options:

  • Daily automatic backup. Requires that you have automatic backups enabled and an available backup to use. If you are creating a database from an automatic backup, you can choose any level 0 weekly backup, or a level 1 incremental backup created after the most recent level 0 backup. For more information on automatic backups, see Automatic Incremental and Archived Redo Log Backups.
  • On-demand full backup. See To create an on-demand full backup of a database for information on creating an on-demand backup.
  • Standalone backup. For more information, see Standalone Backups.
  • Last archived redo log backup. Requires that you have automatic backups enabled. This backup combines data from the most recent daily automatic backup and data from archived redo logs, and represents the most current backup available. The time of the last archived redo log backup is visible on the database details page in the Last Backup Time field.
  • Point-in-time out of place restore. Specify a timestamp to create a new copy of the database that included data up to a specified point in time. The timestamp must be earlier or equal to the Last Backup Time time displayed on the database details page. Note the following limitations when performing a point-in-time out of place restore:

    • The timestamp must be within the recovery window of the database
    • The timestamp must be available within the database incarnation  of the available automatic backups
    • The timestamp cannot fall within two overlapping database incarnations
    • The create database operation will fail if the database has undergone structural changes since the specified timestamp. Structural changes include operations such as creating or dropping a tablespace.
    • The create database operation cannot be started if another point-in-time database copy operation is in progress.

Using the Console

To create a DB system
To create a DB system from a backup

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 create 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.