Oracle Cloud Infrastructure Documentation

Managing Exadata DB Systems

This topic explains how to launch, start, stop, terminate, scale, manage licenses for, and check the status of 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.

Warning

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.

Prerequisites

  • 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.
  • Exadata DB systems require two separate VCN subnets: a client subnet  for user data and a backup subnet for backup traffic.
  • Do not use a subnet that overlaps with 192.168.128.0/20. This restriction applies to both the client subnet and backup subnet.
  • Oracle requires that you use 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.

    For more information, see DNS in Your Virtual Cloud Network.

  • Important! Properly configure the security list ingress and egress rules, and ensure that the rules you create are stateful (the default). The client subnet must allow TCP and ICMP traffic between all nodes and all ports in the respective subnet. If TCP connectivity fails across nodes, the Exadata DB system fails to provision.

    For example, if the client subnet uses the source CIDR 10.0.5.0/24, create rules as shown in the following example.

    
    Ingress Rules:
    
    Stateless: No
    Source: 10.0.5.0/24 
    IP Protocol: TCP 
    Source Port Range: All 
    Destination Port Range: All
    Allows: TCP traffic for ports: all
    
    Stateless: No
    Source: 10.0.5.0/24 
    IP Protocol: ICMP 
    Type and Code: All
    Allows: ICMP traffic for: all types and codes
    
    Egress Rules:
    
    Stateless: No
    Destination: 10.0.5.0/24 
    IP Protocol: TCP 
    Source Port Range: All
    Destination Port Range: All
    Allows: TCP traffic for ports: all
    
    Stateless: No
    Destination: 10.0.5.0/24
    IP Protocol: ICMP 
    Type and Code: All
    Allows: ICMP traffic for: all types and codes 
    

    For information about creating and editing rules, see Security Lists.

    For the backup subnet, you'll need to configure only an egress rule to allow HTTPS access to Object Storage. For details, see Backing Up an Exadata Database.

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 11.2.0.4 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 11.2.0.4 databases.)

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

Using the Console

To launch an Exadata DB system
To check the status of an Exadata DB system
To start, stop, or reboot an Exadata DB system
To scale an Exadata DB system
To terminate an Exadata 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:

Databases:

Nodes:

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.

The DB system's cloud network (VCN) must be configured with either a service gateway or an internet gateway. For information about service gateways, see Access to Object Storage: Service Gateway.

Note

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

If you use an internet gateway instead of a service gateway, add a route rule with the internet gateway as the target and the destination CIDR block as the IP range listed under Object Storage IP Allocations. For more information, see Route Tables.

Oracle recommends that you update the backup subnet's security list to disallow any access from outside the subnet and allow egress traffic for TCP port 443 (https) on the IP ranges listed under Object Storage IP Allocations. For more information, see Security Lists.

Object Storage IP Allocations
Note

The following procedure is required and must be performed on every compute node in an Exadata DB system. Access to the Oracle Cloud Infrastructure Object Storage service is required for backing up databases, patching, and updating the cloud tooling on an Exadata DB system.

To configure a static route for object store access

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