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.

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

Prerequisites

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 (11.2.0.4) 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 (11.2.0.4) 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 (11.2.0.4) 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 Oracle Cloud Infrastructure Managed Backup Features.
  • 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.

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.

Using the Console

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.

To create a DB system
  1. Open the navigation menu. Click Oracle Database, then click Bare Metal, VM, and Exadata.
  2. Click Create DB System.
  3. On the Create DB System page, provide the basic information for the DB system:

    • Select a compartment: By default, the DB system is created in your current compartment and you can use the network resources in that compartment.
    • Name your DB system: A non-unique, display name for the DB system. An Oracle Cloud Identifier (OCID) uniquely identifies the DB system. Avoid entering confidential information.
    • Select an availability domain: The availability domain  in which the DB system resides.
    • Select a shape type: The shape type you select sets the default shape and filters the shape options in the next field.
    • Select a shape: The shape determines the type of DB system created and the resources allocated to the system. To specify a shape other than the default, click Change Shape, and select an available shape from the list.

      Bare metal shapes
      • BM.DenseIO2.52: Provides a 1-node DB system (one bare metal server), with up to 52 CPU cores, 768 GB memory, and eight 6.4 TB locally attached NVMe drives (51.2 TB total) to the DB system.
      • BM.DenseIO1.36: Limited availability. Provides a 1-node DB system (one bare metal server), with up to 36 CPU cores, 512 GB memory, and nine 3.2 TB locally attached NVMe drives (28.8 TB total) to the DB system.

        Note: BM.DenseO1.36 is available only to monthly universal credit customers existing on or before November 9th, 2018. This shape is available only in the US West (Phoenix), US East (Ashburn), and Germany Central (Frankfurt) regions.

      Virtual machine shapes

      Virtual machine X7 shapes:

      • VM.Standard2.1: Provides a 1-node DB system with 1 core.
      • VM.Standard2.2: Provides a 1- or 2-node DB system with 2 cores.
      • VM.Standard2.4: Provides a 1- or 2-node DB system with 4 cores.
      • VM.Standard2.8: Provides a 1- or 2-node DB system with 8 cores.
      • VM.Standard2.16: Provides a 1- or 2-node DB system with 16 cores.
      • VM.Standard2.24: Provides a 1- or 2-node DB system with 24 cores.

      Virtual machine X5 shapes:

      • VM.Standard1.1: Provides a 1-node DB system with 1 core.
      • VM.Standard1.2: Provides a 1- or 2-node DB system with 2 cores.
      • VM.Standard1.4: Provides a 1- or 2-node DB system with 4 cores.
      • VM.Standard1.8: Provides a 1- or 2-node DB system with 8 cores.
      • VM.Standard1.16: Provides a 1- or 2-node DB system with 16 cores.
      Note

      • X5-based shapes availability is limited to monthly universal credit customers existing on or before November 9th, 2018, in the US West (Phoenix), US East (Ashburn), and Germany Central (Frankfurt) regions.
      • VM.Standard1.1 and VM.Standard2.1 shapes cannot be used for 2-node RAC clusters.
    • Configure the DB system: Specify the following:

      • Total node count: The number of nodes in the DB system, which depends on the shape you select. For virtual machine DB systems, you can specify either one or two nodes, except for VM.Standard2.1 and VM.Standard1.1, which are single-node DB systems.
      • Oracle Database software edition: The database edition supported by the DB system. For bare metal systems, you can mix supported database releases on the DB system to include older database versions, but not editions. The database edition cannot be changed and applies to all the databases in this DB system. Virtual machine systems support only one database.
      • CPU core count: Displays only for bare metal DB systems to allow you to specify the number of CPU cores for the system. (Virtual machine DB system shapes have a fixed number of CPU cores.) The text below the field indicates the acceptable values for that shape. For a multi-node DB system, the core count is evenly divided across the nodes.

        Note

        After you provision the DB system, you can increase the CPU cores to accommodate increased demand. On a bare metal DB system, you scale the CPU cores directly. For virtual machine DB systems, you change the number of CPU cores by changing the shape.
    • Choose Storage Management Software: 1-node virtual machine DB systems only. Select Oracle Grid Infrastructure to use Oracle Automatic Storage Management (recommended for production workloads). Select Logical Volume Manager to quickly provision your DB system using Logical Volume Manager storage management software. Note that the Available storage (GB) value you specify during provisioning determines the maximum total storage available through scaling. The total storage available for each choice is detailed in the Storage Scaling Considerations for Virtual Machine Databases Using Fast Provisioning topic.

      See Fast Provisioning Option for 1-node Virtual Machine DB Systems for more information about this feature.

    • Configure storage: Specify the following:

      • Available storage (GB): Virtual machine only. The amount of Block Storage in GB to allocate to the virtual machine DB system. Available storage can be scaled up or down as needed after provisioning your DB system.
      • Total storage (GB): Virtual machine only. The total Block Storage in GB used by the virtual machine DB system. The amount of available storage you select determines this value. Oracle charges for the total storage used.
      • Cluster name: (Optional) A unique cluster name for a multi-node DB system. The name must begin with a letter and contain only letters (a-z and A-Z), numbers (0-9) and hyphens (-). The cluster name can be no longer than 11 characters and is not case sensitive.
      • Data storage percentage: Bare metal only. The percentage (40% or 80%) assigned to DATA storage (user data and database files). The remaining percentage is assigned to RECO storage (database redo logs, archive logs, and recovery manager backups).
    • Add SSH key: Add the public key portion of each key pair you want to use for SSH access to the Exadata system. Select on of the following options:

      • Generate SSH key pair: Use this option to create a new SSH key pair. Click both Save Private Key and Save Public Key when using this option. The private key is downloaded to your local machine, and should be stored in a safe location. You cannot download another copy of the private key generated during this operation after completing the operation.
      • Upload SSH key files: Select this option to browse or drag and drop .pub files.
      • Paste SSH keys: Select this option to paste in individual public keys. To paste multiple keys, click + Another SSH Key, and supply a single key for each entry.
    • Choose a license type: The type of license you want to use for the DB system. Your choice affects metering for billing.

      • License Included means the cost of this Oracle Cloud Infrastructure Database service resource will include both the Oracle Database software licenses and the service.
      • Bring Your Own License (BYOL) means you will use your organization's Oracle Database software licenses for this Oracle Cloud Infrastructure Database service resource. See Bring Your Own License for more information.
  4. Specify the network information:

    • Virtual cloud network: The VCN in which to create the DB system. Click Change Compartment to select a VCN in a different compartment.
    • Client Subnet: The subnet to which the DB system attaches. For 1- and 2-node RAC DB systems:  Do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet causes the private interconnect to malfunction.

      Click Change Compartment to select a subnet in a different compartment.

    • Network Security Groups: Optionally, you can specify one or more network security groups (NSGs) for your DB system. NSGs function as virtual firewalls, allowing you to apply a set of ingress and egress security rules to your DB system. A maximum of five NSGs can be specified. For more information, see Network Security Groups and Network Setup for DB Systems.

      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.

      To use network security groups
      1. Check the Configure Network Security Groups check box. Note that you must have a virtual cloud network selected to be able to assign NSGs to your DB system.
      2. Specify the NSG to use with the DB system. You might need to use more than one NSG. If you're not sure, contact your network administrator.
      3. To use additional NSGs, click + Another Network Security Group.
    • Hostname prefix: Your choice of host name for the bare metal or virtual machine DB system. The host name must begin with an alphabetic character, and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed for bare metal and virtual machine DB systems is 16.

      Important

      The host name must be unique within the subnet. If it is not unique, the DB system will fail to provision.
    • Host domain name: The domain name for the DB system. If the selected subnet uses the Oracle-provided Internet and VCN Resolver for DNS name resolution, then this field displays the domain name for the subnet and it can't be changed. Otherwise, you can provide your choice of a domain name. Hyphens (-) are not permitted.
    • Host and domain URL: Combines the host and domain names to display the fully qualified domain name (FQDN) for the database. The maximum length is 64 characters.
    • Private IP address: Optionally, for non-RAC DB systems, you can define the IP address of the new DB system. This is useful in development contexts where you create and delete a DB system over and over, and you need each new iteration of the DB system to use the same IP address. If you specify an IP address that is currently in use within the subnet, the provisioning operation will fail with an error message regarding the invalid IP address.
  5. Click Show Advanced Options to specify advanced options for the DB system:

    • Disk redundancy: For bare metal systems only. The type of redundancy configured for the DB system.
      • Normal is 2-way mirroring, recommended for test and development systems.
      • High is 3-way mirroring, recommended for production systems.
    • Fault domain: The fault domain(s) in which the DB system resides. You can choose which fault domain to use for your DB system. For two-node Oracle RAC DB systems, you can specify which two fault domains to use. Oracle recommends that you place each node of a two-node Oracle RAC DB system in a different fault domain. For more information on fault domains, see About Regions and Availability Domains.
    • Time zone: The default time zone for the DB system is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system. For more information, see DB System Time Zone.

      Tip

      If you want to set a time zone other than UTC or the browser-detected time zone, and if you do not see the time zone you want, try selecting "Miscellaneous" in the Region or country list.

    • Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
  6. After you complete the network configuration and specify any advanced options, click Next.
  7. Provide information for the initial database:

    • Database name: The name for the database, also known as the DB_NAME. The database name must begin with an alphabetic character and can contain a maximum of eight alphanumeric characters. Special characters are not permitted.
    • Database unique name suffix: Optional. The second portion of the database unique name. The complete database unique name is created by appending the database unique name suffix to the database name you specify.
    • Database unique name: This read-only field displays the complete database unique name (DB_UNIQUE_NAME). The database unique name is a globally unique name for the database. Primary and standby databases in a Data Guard association can share the same database name, but must have different database unique names.
    • Database image: Determines what Oracle Database version is used for the database. You can mix database versions on the DB system, but not editions. By default, the latest Oracle-published database software image is selected.

      Click Change Database Image to use an older Oracle-published image or a custom database software image that you have created in advance, then select an Image Type:

      • Oracle Provided Database Software Images: These images contain generally available versions of Oracle Database software.
      • Custom Database Software Images: These images are created by your organization and contain customized configurations of software updates and patches. Use the Select a compartment and Select a Database version selectors to limit the list of custom database software images to a specific compartment or Oracle Database software major release version.

        Important

        The custom database software image must be based on an Oracle Database release that meets the following criteria:

        • The release is currently supported by Oracle Cloud Infrastructure
        • The release is supported by the hardware model you are provisioning

      After choosing a software image, click Select to return to the Create Database dialog.

    • PDB name: Not applicable to Oracle Database 11g (11.2.0.4). The name of the pluggable database. The PDB name must begin with an alphabetic character, and can contain a maximum of eight alphanumeric characters. The only special character permitted is the underscore (_).
    • Create administrator credentials: A database administrator SYS user will be created with the password you supply.

      • Username: SYS
      • Password: Supply the password for this user. The password must meet the following criteria:

        A strong password for SYS, SYSTEM, TDE wallet, and PDB Admin. The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the username (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.
      • Confirm password: Re-enter the SYS password you specified.
      • Using a TDE wallet password password is optional. If you are using customer-managed encryption keys stored in a vault in your tenancy, the TDE wallet password is not applicable to your DB system. Use Show Advanced Options at the end of the Database Information section to configure customer-managed keys.

        If you are using customer-managed keys, or if you want to specify a different TDE wallet password, uncheck the Use the administrator password for the TDE wallet box. If you are using customer-managed keys, leave the TDE password fields blank. To set the TDE wallet password manually, enter a password in the Enter TDE wallet password field, and then confirm by entering it into the Confirm TDE wallet password field.

    • Select workload type: Choose the workload type that best suits your application:

      • Online Transactional Processing (OLTP) configures the database for a transactional workload, with a bias towards high volumes of random data access.
      • Decision Support System (DSS) configures the database for a decision support or data warehouse workload, with a bias towards large data scanning operations.
    • Configure database backups: Specify the settings for backing up the database to Object Storage:

      • Enable automatic backup: Check the check box to enable automatic incremental backups for this database. If you are creating a database in a security zone compartment, you must enable automatic backups.
      • Backup retention period: If you enable automatic backups, then you can choose one of the following preset retention periods: 7 days, 15 days, 30 days, 45 days, or 60 days. The default selection is 30 days.
      • Backup Scheduling: If you enable automatic backups, then you can choose a two-hour scheduling window to control when backup operations begin. If you do not specify a window, then the six-hour default window of 00:00 to 06:00 (in the time zone of the DB system's region) is used for your database. See Backup Scheduling for more information.
    • Click Show Advanced Options to specify advanced options for the initial database.

      In the Management tab, you can set the following options:

      • Character set: The character set for the database. The default is AL32UTF8.
      • National character set: The national character set for the database. The default is AL16UTF16.

      In the Encryption tab, configure the encryption key management option for your database. By default, the database is configured using Oracle-managed encryption keys. To configure the database with encryption based on encryption keys you manage:

      1. Select Use customer-managed keys. You must have a valid encryption key in Oracle Cloud Infrastructure Vault service. See Let security admins manage vaults, keys, and secrets.
        Note

        You must use AES-256 encryption keys for your database.
      2. Choose a Vault.
      3. Select a Master encryption key.
      4. To specify a key version other than the latest version of the selected key, check Choose the key version and enter the OCID of the key you want to use in the Key version OCID field.

      In the Tags tab, you can add free-form tags or defined tags to this resource. You must have permissions to use the tag namespace for defined tags. See Resource Tags for information about using tags to manage your OCI resources.

  8. Click Create DB System. The DB system appears in the list with a status of Provisioning. The DB system's icon changes from yellow to green (or red to indicate errors).

    After the DB system's icon turns green, with a status of Available, you can click the highlighted DB system name to display details about the DB system. Note the IP addresses. You'll need the private or public IP address, depending on network configuration, to connect to the DB system.

To create a DB system from a backup

You can create a new DB system from a backup. See Using a Backup to Create the Initial Database in this topic for details on backup source options.

Before you begin, note the following:

  • When you create a DB system from a backup, the availability domain is the same as where the backup is hosted.
  • The shape you specify must be the same type as the database from which the backup was taken. For example, if you are using a backup of a single-node database, then the DB system you select as your target must also be a single-node DB system.
  • The Oracle database software version you specify must be an equal or greater version than that of the backed up database.
  • If you specify a virtual machine DB system shape, then the Available Storage Size will default to the data size of the backup, rounded up to the closest storage size option. However, you can specify a larger storage size.
  • If you are creating a new DB system from an automatic backup, you may 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 Oracle Cloud Infrastructure Managed Backup Features
  • If the backup being used to create a DB system is in a security zone compartment, the DB system cannot be created in a compartment that is not in a security zone. See the Security Zone Policies topic for a full list of policies that affect Database service resources.
  1. Open the navigation menu. Click Oracle Database, then click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. Navigate to the backup or standalone backup you want to use to create the new DB system:

    Tip

    If you are creating a database from an automatic backup, you may 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 Oracle Cloud Infrastructure Managed Backup Features.
    To select a daily automatic backup or on-demand full backup as the source
    1. Find the DB system where the database is located, and click the system name to display details about it.
    2. From the Databases list, click the source database name.
    3. Find your desired backup in the Backups list.  If you don't see the backups list on the database details page, click Backups in the Resources menu.
    4. Click the Actions menu for the backup, and then click Create Database.
    5. In the Create Database from Backup dialog, select Create a new DB system.
    6. Click Create.
    To select the last archived redo log automatic backup as the source
    1. Find the DB system where the database is located, and click the system name to display details about it.
    2. Find the database associated with the backup you wish to use, and click its name to display details about it.
    3. On the database details page, click Create Database from Backup.
    4. In the Create Database from Backup dialog, select the following:

      • Create database from last backup
      • Create a new DB system
    5. Click Create.
    To specify a timestamp for a point-in-time copy of the source
    1. Find the DB system where the database is located, and click the system name to display details about it.
    2. Find the database associated with the backup you wish to use, and click its name to display details about it.
    3. On the database details page, click Create Database from Backup.
    4. In the Create Database from Backup dialog, do the following:

      1. Select Create database from specified timestamp.
      2. In the Restore timestamp field, enter a timestamp. The restore timestamp determines the most recent data that will be included in the restored version of the database.
      3. Select Create a new DB system.
      4. Click Create.
    To select a standalone backup as the source
    1. Click Standalone Backups under Bare Metal, VM, and Exadata.
    2. In the list of standalone backups, find the backup you want to use to create the database.
    3. Click the Actions menu for the backup you are interested in, and then click Create Database.
    4. In the Create Database from Backup dialog, select Create a new DB system.
    5. Click Create.
  4. In the Create Database from Backup dialog, enter the DB system information:

    • Select a compartment: Select a compartment for your new DB system.
    • Name your DB system: Enter a friendly, display name for the DB system. The name doesn't need to be unique. An Oracle Cloud Identifier (OCID) will uniquely identify the DB system.

    • Select a shape type: Specify either Virtual Machine or Bare Metal.
    • Select a shape: Specify a shape to use to launch the DB system. The shape determines the type of DB system and the resources allocated to the system. Click Change Shape to see available shapes.

      The selected shape must support the same number of nodes as the DB system from which the backup was created.

      Bare metal shapes
      • BM.DenseIO2.52: Provides a 1-node DB system (one bare metal server), with up to 52 CPU cores, 768 GB memory, and eight 6.4 TB locally attached NVMe drives (51.2 TB total) to the DB system.
      • BM.DenseIO1.36: Limited availability. Provides a 1-node DB system (one bare metal server), with up to 36 CPU cores, 512 GB memory, and nine 3.2 TB locally attached NVMe drives (28.8 TB total) to the DB system.

        Note: BM.DenseO1.36 is available only to monthly universal credit customers existing on or before November 9th, 2018. This shape is available only in the US West (Phoenix), US East (Ashburn), and Germany Central (Frankfurt) regions.

      Virtual machine shapes

      Virtual machine X7 shapes:

      • VM.Standard2.1: Provides a 1-node DB system with 1 core.
      • VM.Standard2.2: Provides a 1- or 2-node DB system with 2 cores.
      • VM.Standard2.4: Provides a 1- or 2-node DB system with 4 cores.
      • VM.Standard2.8: Provides a 1- or 2-node DB system with 8 cores.
      • VM.Standard2.16: Provides a 1- or 2-node DB system with 16 cores.
      • VM.Standard2.24: Provides a 1- or 2-node DB system with 24 cores.

      Virtual machine X5 shapes:

      • VM.Standard1.1: Provides a 1-node DB system with 1 core.
      • VM.Standard1.2: Provides a 1- or 2-node DB system with 2 cores.
      • VM.Standard1.4: Provides a 1- or 2-node DB system with 4 cores.
      • VM.Standard1.8: Provides a 1- or 2-node DB system with 8 cores.
      • VM.Standard1.16: Provides a 1- or 2-node DB system with 16 cores.
      Note

      • X5-based shapes availability is limited to monthly universal credit customers existing on or before November 9th, 2018, in the US West (Phoenix), US East (Ashburn), and Germany Central (Frankfurt) regions.
      • VM.Standard1.1 and VM.Standard2.1 shapes cannot be used for 2-node RAC clusters.
    • For virtual machine DB systems, specify the following:

      • Total Node Count: The number of nodes in the DB system. The number depends on the shape you select. You can specify 1 or 2 nodes for virtual machine DB systems, except for VM.Standard2.1 and VM.Standard1.1, which are single-node DB systems.
      • Oracle Database Software Edition: The database edition supported by the DB system. For bare metal systems, you can mix supported database releases on the DB system to include older database versions, but not editions. The database edition cannot be changed and applies to all the databases in this DB system. Virtual machine systems support only one database.
      • Storage management software: Oracle Grid Infrastructure use Oracle's storage management software and is recommended for production environments. Logical Volume Manager is available for fast provisioning and is recommended for test and development systems.
      • Available storage (GB): Enter the amount of Block Storage you wish to allocate to the virtual machine DB system for your data files. The read-only Total storage field displays the total amount of storage that will be used by the DB system, including storage required by Oracle's DB system software. The minimum value for available storage is determined by the size of the backup.
    • For bare metal DB systems, specify the following:

      • Oracle Database Software Edition: The database edition supported by the DB system. For bare metal systems, you can mix supported database releases on the DB system to include older database versions, but not editions. The database edition cannot be changed and applies to all the databases in this DB system. Virtual machine systems support only one database.
      • CPU core count: Specify a number of CPU cores to enable on the DB System. You must specify a multiple of 2, up to 36.
      • Data storage percentage: The percentage (40% or 80%) assigned to DATA storage (user data and database files). The remaining percentage is assigned to RECO storage (database redo logs, archive logs, and recovery manager backups).
      • Disk redundancy: The type of redundancy configured for the DB system.

        • Normal is 2-way mirroring, recommended for test and development systems.
        • High is 3-way mirroring, recommended for production systems.
    • Add SSH keys: Add the public key portion of the key pair you want to use for SSH access to the DB system. You can add keys in three ways:

      • Generate SSH key pair: Use this option to create a new key SSH key pair. Important: you must click Save Private Key if using this option during the DB system creation. The private key created with this option cannot be downloaded or retrieved after system creation is complete. After you save the private key, click Save Public Key to save a copy of the public key file.
      • Upload SSH key files: Drag and drop your existing public key file, or click the browse link to navigate to a public key stored on your local machine.
      • Paste SSH keys: Paste your key directly into this field. To provide multiple keys, paste each key on a new line. Make sure each key is on a single, continuous line. The length of the combined keys cannot exceed 10,000 characters.
    • License Type: The type of license you want to use for the DB system. Your choice affects metering for billing.
      • License included means the cost of this Oracle Cloud Infrastructure Database service resource will include both the Oracle Database software licenses and the service.
      • Bring Your Own License (BYOL) means you will use your organization's Oracle Database software licenses for this Oracle Cloud Infrastructure Database service resource. See Bring Your Own License for more information.
  5. Specify the network information: In this section of the dialog, enter the networking information for your DB system:

    • Virtual Cloud Network: The VCN in which to launch the DB system.
    • Client Subnet: The subnet to which the bare metal or virtual machine DB system should attach. For 1- and 2-node RAC DB systems:  Do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet causes the private interconnect to malfunction.
    • Network Security Groups: Optionally, you can specify one or more network security groups (NSGs) for your DB system. NSGs function as virtual firewalls, allowing you to apply a set of ingress and egress security rules to your DB system. A maximum of five NSGs can be specified. For more information, see Network Security Groups and Network Setup for DB Systems.

      To use network security groups
      1. Check the Use Network Security Groups check box. Note that you must have a virtual cloud network selected to be able to assign NSGs to your DB system.
      2. Specify the NSG to use with the DB system. You might need to use more than one NSG. If you're not sure, contact your network administrator.
      3. To use additional NSGs, click + Another Network Security Group.
    • Hostname Prefix: Your choice of host name for the bare metal or virtual machine DB system. The host name must begin with an alphabetic character, and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed for bare metal and virtual machine DB systems is 16.
      Important

      The host name must be unique within the subnet. If it is not unique, the DB system will fail to provision.
    • Private IP address: Optionally, for non-RAC DB systems, you can define the IP address of the new DB system. This is useful in development contexts where you create and delete a DB system over and over, and you need each new iteration of the DB system to use the same IP address. If you specify an IP address that is currently in use within the subnet, the provisioning operation will fail with an error message regarding the invalid IP address.
  6. Show Advanced Options: Click this link to access the following options:

    • Fault Domain: The fault domains in which the DB system resides. You can choose which fault domain to use for your DB system. For 2-node RAC DB systems, you can specify which two fault domains are to be used. Oracle recommends that you place each node of a 2-node RAC DB system in a different fault domain. For more information on fault domains, see Fault Domains.
    • Time Zone: Specify a time zone for your DB system.

      • UTC: configures your DB system to use coordinated universal time.
      • Browser-detected: The console displays the time zone detected by your browser for this option.
      • Select another time zone: To manually specify a time zone, first make a choice using the Region or country selector to select a geographic region, then use the Time zone selector to select your desired time zone.
    • Tags: Apply an OCI tag to your DB system resource. See Tagging Overview for more information.
  7. Click Next to advance to the Database Information screen. Provide the following information for the initial database:

    • Database name: The name for the database. The database name must begin with an alphabetic character and can contain a maximum of eight alphanumeric characters. Special characters are not permitted.
    • Database unique name suffix: The second portion of the database unique name. The complete database unique name is created by appending the database unique name suffix to the database name you specify.
    • Database unique name: This read-only field displays the complete database unique name (DB_UNIQUE_NAME). The database unique name is a globally unique name for the database. Primary and standby databases in a Data Guard association can share the same database name, but must have different database unique names.
    • Database image: Optional. You can specify what Oracle Database version is used for the database. You can mix database versions on the DB system, but not editions. By default, the latest Oracle-published database software image is selected.

      Click Change Database Image to choose a custom database software image that you or someone in your organization have created in your tenancy.

      Select a Compartment and a Database version. Then select a database image from the table of available images for the Oracle Database version you selected.

      After choosing a software image, click Select to return to the Create Database dialog.

    • Password: Specify a strong password to be used for the SYS and SYSTEM users, the TDE wallet (if applicable), and the PDB Admin user. The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the username (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.
    • Confirm password: Re-enter the database admin password you specified.
    • Enter the source database's TDE wallet or RMAN password: (Applies only to databases using Oracle-managed encryption keys).

      Enter either the TDE wallet password or the RMAN encryption password for the backup, whichever is applicable. The TDE wallet password is the SYS password provided when the database was created by using the Oracle Cloud Infrastructure Console, API, or CLI. The RMAN encryption password is typically required instead if the password was subsequently changed manually.

  8. Click Create 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:

Databases:

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 example.com and you want to use clouddb1 as the host name, you would request a DNS record that associates clouddb1.example.com 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 register.com.
  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.