Oracle Cloud Infrastructure Documentation

Creating Exadata DB Systems

This topic explains how to launch an Exadata DB system. It also describes how to configure required access to the Oracle Cloud Infrastructure Object Storage service and set up DNS.

When you launch an Exadata DB system using the Console or the API, the system is provisioned to support Oracle databases. The service creates an initial database 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. If you want to dig deeper into writing policies for databases, see Details for the Database Service.


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

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.

  • 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 database home
  • Database Language: AMERICAN
  • Database Sizing Template: odb2
  • Database Storage: Automatic Storage Management (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 in the Console, see To create an Exadata DB system.

Using the Console

To create an Exadata DB system

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:

Configuring a Static Route for Accessing the Object Store

All the traffic in an Exadata DB system is, by default, routed through the data network. To route backup traffic to the backup interface (BONDETH1), you need to configure a static route on each of the compute nodes in the cluster. For instructions, see Node Access to Object Storage: Static Route.

Setting Up DNS for a DB System

DNS lets you use hostnames 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. Oracle recommends using a VCN Resolver for DNS name resolution for the client subnet. It automatically resolves the Swift endpoints required for backing up databases, patching, and updating the cloud tooling on an Exadata DB system.