Overview of the Database Service

The Database service offers autonomous and co-managed Oracle Database cloud solutions. Autonomous databases are preconfigured, fully-managed environments that are suitable for either transaction processing or for data warehouse workloads. Co-managed solutions are bare metal, virtual machine, and Exadata DB systems that you can customize with the resources and settings that meet your needs.

You can quickly provision an autonomous database or co-managed DB system. You have full access to the features and operations available with the database, but Oracle owns and manages the infrastructure.

You can also extend co-managed database services into your data center by using Exadata Cloud@Customer, which applies the combined power of Exadata and Oracle Cloud Infrastructure while enabling you to meet your organization's data-residency requirements.

For details about each offering, start with the following overview topics:

Autonomous Databases

The Database service offers Oracle's Autonomous Database with transaction processing and data warehouse workload types.

Co-managed Systems

Note

For information about MySQL Database, see MySQL Database.

License Types and Bring Your Own License (BYOL) Availability

Database Service License Options

Oracle Cloud Infrastructure supports a licensing model with two license types. With License included, the cost of the cloud service includes a license for the Database service. With Bring Your Own License (BYOL), Oracle Database customers can use existing licenses with Oracle Cloud Infrastructure. Note that Oracle Database customers remain responsible for complying with license restrictions applicable to their BYOL licenses, as defined in their program order for those licenses.

You do not need separate on-premises licenses and cloud licenses. BYOL databases support all advanced Database service manageability functionality, including backing up and restoring a DB system, patching, and Oracle Data Guard.

You can choose BYOL when you launch a cloud-hosted Oracle Cloud Infrastructure database or DB system. Choosing BYOL impacts how the usage data for the instance is metered and subsequent billing. You can also switch license types after provisioning.

Note that on some provisioning dialogs in the Console, the BYOL option is labeled My Organization Already Owns Oracle Database Software Licenses.

For additional information about license pricing and features, see Oracle Cloud Database Services. For guidelines on using Oracle Database licenses, see Database Licensing.

Moving Database Resources to a Different Compartment

You can move DB systems, Autonomous Database resources, and Exadata Cloud@Customer resources from one compartment to another. When you move a Database resource to a new compartment, its dependent resources move with it. After you move the resource to the new compartment, inherent policies apply immediately and affect access to that resource and its dependent resources through the Console.

Important

To move resources between compartments, resource users must have sufficient access permissions on the compartment that the resource is being moved to, as well as the current compartment. For more information about permissions for Database resources, see Details for the Database Service.

Dependent Resource Details

Details about dependent resources are as follows:

  • Bare metal, virtual machine, and Exadata DB systems: Dependent resources that move with these DB systems include Database Homes and databases, as well as the metadata for automatic backups. To verify the compartment of a dependent resource, check the compartment of the DB system.
  • Autonomous Database: Autonomous Database dependent resources are limited to its automatic backups. Autonomous Exadata Infrastructure instances and Autonomous Container Databases have no dependent resources that move with them. Associated (non-dependent) resources remain in their current compartments.
  • Exadata Cloud@Customer: Resources that can be moved are Exadata Infrastructure, VM clusters, and backup destinations. VM cluster networks are dependent resources of Exadata Infrastructure instances, so they move with them. VM clusters have the following dependent resources: Database Homes, and databases and their automatic backups. Backup destinations have no dependent resources.

For more information about moving resources to other compartments, see To move a resource to a different compartment.

Monitoring Resources

You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring Overview and Notifications Overview.

For information about available Database service metrics and how to view them, see Database Metrics.

Creating Automation with Events

You can create automation based on state changes for your Oracle Cloud Infrastructure resources by using event types, rules, and actions. For more information, see Overview of Events.

See Database for details about Database resources that emit events.

Resource Identifiers

Most types of Oracle Cloud Infrastructure resources have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID). For information about the OCID format and other ways to identify your resources, see Resource Identifiers.

Ways to Access Oracle Cloud Infrastructure

You can access Oracle Cloud Infrastructure using the Console (a browser-based interface) or the REST API. Instructions for the Console and API are included in topics throughout this guide. For a list of available SDKs, see Software Development Kits and Command Line Interface.

To access the Console, you must use a supported browser. You can use the Console link at the top of this page to go to the sign-in page. You will be prompted to enter your cloud tenant, your user name, and your password.

For more information, see Key Concepts and Terminology and Key Concepts and Terminology. For general information about using the API, see REST APIs. For information on deprecated Database Service APIs, see Deprecated Database Service APIs

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to write policies that provide stricter access to database resources, see Details for the Database Service.

Authentication and Authorization

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

An administrator in your organization needs to set up groups , compartments , and policies  that control which users can access which services, which resources, and the type of access. For example, the policies control who can create new users, create and manage the cloud network, launch instances, create buckets, download objects, etc. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see Policy Reference.

If you’re a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.

For common policies used to authorize Oracle Cloud Infrastructure Database users, see Common Policies.

For in-depth information on granting users permissions for the Database service, see Details for the Database Service in the IAM policy reference.

Limits on the Database Service

See Service Limits for a list of applicable limits and instructions for requesting a limit increase. To set compartment-specific limits on a resource or resource family, administrators can use compartment quotas.

Note

Service limits and compartment quotas do not apply to Exadata Cloud@Customer.

Many Database API operations are subject to throttling.

Work Requests Integration

The Database service is integrated with the Oracle Cloud Infrastructure Work Requests API. Work requests allow you to monitor long-running operations such as the provisioning of DB systems. A work request is an activity log that enables you to track each step in the operation's progress. Each work request has an OCID  that allows you to interact with it programmatically and use it for automation. For general information on using work requests in Oracle Cloud Infrastructure, see Work Requests and the Work Requests API.

Database service operations that create work requests

The following Database operations result in the creation of a work request:

Autonomous Databases

  • Creating or terminating the following resource types: 

    • Autonomous Databases
    • Autonomous Container Databases
    • Autonomous Exadata Infrastructure instances
  • Starting or stopping an Autonomous Database instance
  • Restoring an Autonomous Database instance
  • Cloning an Autonomous Database instance
  • Creating or deleting manual backups
  • Scaling database storage or CPU (includes enabling or disabling CPU auto scaling)
  • Updating the database license type
  • Updating a database's network access control list (ACL)
  • Moving the following resource types to a different compartment:

    • Autonomous Databases
    • Autonomous Container Databases
    • Autonomous Exadata Infrastructure instances

Bare Metal Databases

  • Creating and terminating (or deleting) the following resource types: 

    • DB systems
    • Databases
    • Database homes
    • Database backups
    • Oracle Data Guard associations
  • Creating DB systems from a backup
  • Patching DB systems
  • Patching database homes
  • Restoring a database
  • Performing the following Oracle Data Guard operations:

    • Switchover
    • Failover
    • Reinstate
  • Scaling CPU cores
  • Moving a DB system to a different compartment
  • Performing the following node operations:

    • Start node
    • Stop node
    • Reboot node
    • Soft reset of node
  • Registering or deregistering an Autonomous Database with Data Safe.

Virtual Machine Databases

  • Creating and terminating (or deleting) the following resource types: 

    • DB systems (includes the creation or termination of the database contained within the DB system)
    • Database backups
    • Oracle Data Guard associations
  • Creating DB systems from a backup
  • Patching a DB system
  • Restoring a database
  • Performing the following Oracle Data Guard operations:

    • Switchover
    • Failover
    • Reinstate
  • Scaling storage
  • Moving a DB system to a different compartment
  • Performing the following node operations:

    • Start node
    • Stop node
    • Reboot node
    • Soft reset of node
Note

Virtual machine databases are created and terminated as part of the creation or termination of the DB system containing the database. Virtual machine DB systems can contain only one database.

Exadata Databases

  • Creating and terminating (or deleting) the following resource types: 

    • DB systems
    • Database homes
    • Databases
    • Database backups
    • Oracle Data Guard associations
  • Restoring a database
  • Performing the following Oracle Data Guard operations:

    • Switchover
      • Failover
    • Reinstate
  • Scaling CPU cores
  • Adding an SSH key
  • Configuring the I/O Resource Manager (IORM)
  • Moving a DB system to a different compartment
  • Performing the following node operations:

    • Start node
    • Stop node
    • Reboot node
    • Soft reset of node

Exadata Cloud@Customer Databases

  • Creating and terminating (or deleting) the following resource types: 

    • Exadata infrastructure
    • Create VM cluster

    • VM cluster network
    • Exadata database
  • Activate Exadata infrastructure
  • Update Exadata infrastructure
  • Validate VM cluster network
  • Update VM cluster network
  • Update SSH key
  • Update CPU count
  • Update VM cluster license type
  • Change VM cluster compartment
  • Start, stopping, and rebooting a VM cluster node
  • Update database
  • Restore database

Getting Oracle Support Help for Your Database Resources

You can easily open a My Oracle Support ticket for individual Database resources while viewing them in the Oracle Cloud Infrastructure Console. For more information, see Getting Help and Contacting Support.