Overview of Creating a DB System
This article provides an introduction about various settings required 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.
Creating a new DB system that uses Oracle Database 18c is not supported. However, creating a new DB system from a backup that uses Oracle Database 18c is supported.
Required IAM Policy
To use Oracle Cloud Infrastructure, you must be granted security access in a policy by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment to work in.
For administrators: The policy in Let database admins manage Oracle Cloud 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 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 VCN and Subnets.
- 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 VCN and Subnets.
- 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 (188.8.131.52) 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: Oracle Automatic Storage Management Cluster File System (ACFS) for Oracle Database 11g (184.108.40.206) databases. Otherwise, Automatic Storage Management (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 (220.127.116.11) databases.)
For more information on ASM, see Automatic Storage Management. For a list of the database options that you can set, see Create a DB System Using the Console.
Use a Backup to Create the Initial Database
When creating a new DB system using a backup stored in the Recovery Service or 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.
- On-demand full backup.
- Standalone backup.
- 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.
For more information on backups, see Back Up a Database Using the Console.
Custom IP Addresses for Non-RAC DB Systems
When creating a new non-RAC DB system or cloning an existing VM DB system, you can optionally define the IP address of the DB system being provisioned. This is useful in development contexts where you create and delete the same DB system over and over, and you need each new iteration of the DB system to use the same IP address.
Use 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.
Shapes and database versions:
For the complete list of APIs for the Database service, see Database Service API.