Oracle Cloud Infrastructure Documentation

Managing Databases on Exadata Cloud at Customer

This topic explains how to manage Oracle databases on Exadata Cloud at Customer.

Before you can create and use Oracle databases on Exadata Cloud at Customer, you must:

  • Provision Exadata Cloud at Customer infrastructure.
  • Configure a VM cluster.
  • Create any required backup destinations.

You can create one or more databases on each Exadata Cloud at Customer system. Apart from the inherent storage and processing capacity of your Exadata system, there is no set maximum for the number of databases that you can create.

By default, databases on Exadata Cloud at Customer use Oracle Database Enterprise Edition - Extreme Performance. This edition provides all the features of Oracle Database Enterprise Edition, plus all the database enterprise management packs and all the Enterprise Edition options, such as Oracle Database In-Memory and Oracle Real Application Clusters (RAC). If you are using your own Oracle Database licenses, then your ability to use various features is limited by your license holdings.

Exadata Cloud at Customer supports the following Oracle Database software releases:

  • Oracle Database 19c
  • Oracle Database 18c
  • Oracle Database 12c Release 2
  • Oracle Database 12c Release 1
  • Oracle Database 11g Release 2

When you provision a database, you can associate it with a backup destination and enable automatic backups. For more information, see Managing Backup Destinations for Exadata Cloud at Customer and Managing Database Backup and Recovery on Exadata Cloud at Customer.

Each Oracle database is configured as follows:

  • Each database is configured with Oracle RAC database instances running on every node in the VM cluster.
  • Each database uses a separate set of Oracle binaries in a separate Oracle home location.
  • Each database is configured with default instance parameter settings. While the defaults are reasonable for many cases, you should review the instance parameter settings to ensure that they meet your specific application needs.

    In particular, consider the Oracle Database system global area (SGA) and program global area (PGA) instance parameter settings, especially if your VM cluster supports multiple databases. And, ensure that the sum of all Oracle Database memory allocations never exceeds the available physical memory on each compute node.

  • Each database using Oracle Database 12c Release 1, or later, is configured as a container database (CDB) and one pluggable database (PDB) is created inside the CDB. By default:

    • The first PDB is configured with a local PDB administration user account named PDBADMIN.
    • The PDBADMIN user account is initially configured with the same administration password as the CDB SYS and SYSTEM users.
    • The PDBADMIN user account is initially configured with basic privileges assigned through two roles; CONNECT and PDB_DBA. However, for most practical administration purposes you must assign extra privileges to the PDBADMIN user account or the PDB_DBA role.

    You can use native Oracle Database facilities to create extra PDBs and to manage all of your PDBs. The dbaascli utility also provides a range of convenient PDB management functions. See Using the dbaascli Utility on Exadata Cloud at Customer.

  • Depending on the Oracle Database version in use, each database contains web-based monitoring and management tools provided by Enterprise Manager Database Express (EM Express) or Enterprise Manager Database Control (Database Control). See Using EM Express and Database Control on Exadata Cloud at Customer. The dbaascli utility also provides a range of convenient database management functions. See Using the dbaascli Utility on Exadata Cloud at Customer.

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

Using the Console

To create a database
To terminate a database

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

Database homes:

Databases:

Nodes:

For the complete list of APIs, see Database Service API.