The Database service offers autonomous and user-managed Oracle Database solutions. Autonomous databases are preconfigured, fully-managed environments that are suitable for either transaction processing or for data warehouse workloads. User-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 user-managed DB system. You have full access to the features and operations available with the database, but Oracle owns and manages the infrastructure.
For details about each offering, start with the following overview topics:
The Database service offers Oracle's Autonomous Database with transaction processing and data warehouse workload types.
License Types and Bring Your Own License (BYOL) Availability
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 an Oracle Cloud Infrastructure database or DB system. Choosing BYOL impacts how the usage data for the instance is metered and subsequent billing.
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 https://cloud.oracle.com/database/pricing.
You can move DB systems and autonomous databases from one compartment to another. When you move a DB system or autonomous database to a new compartment, its dependent resources move with it. After you move the DB system or autonomous database to the new compartment, inherent policies apply immediately and affect access to the DB system or autonomous database and dependent resources through the Console.
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 resources that move with DB systems include DB 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 dependent resources are limited to its automatic backups. Autonomous Exadata Infrastructures and Autonomous Container Databases have no dependent resources that move with them. Associated (non-dependent) resources remain in their current compartments.
For more information about moving resources to other compartments, see Moving Resources to a Different Compartment.
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.
The following Database resources emit events:
- Autonomous Databases
- Autonomous Container Databases
- Autonomous Exadata Infrastructure instances
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.
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.
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 A collection of users who all need a particular type of access to a set of resources or compartment., A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization., and 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. 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.
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.
Many Database API operations are subject to throttling.
- Overview of the Database Service
- License Types and Bring Your Own License (BYOL) Availability
- Moving Database Resources to a Different Compartment
- Creating Automation with Events
- Resource Identifiers
- Ways to Access Oracle Cloud Infrastructure
- Authentication and Authorization
- Limits on the Database Service