MySQL Database Service is a fully-managed Oracle Cloud Infrastructure native service, developed, managed, and supported by the MySQL team in Oracle. Oracle automates all tasks such as backup and recovery, database and operating system patching, and so on. You are responsible solely for managing your data, schema designs, and access policies.
This documentation is intended for MySQL Server Administrators and assumes familiarity with MySQL Server and tools. For additional information, see the product documentation available at MySQL Documentation.
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 the latest information on the regions where MySQL Database Service is available, see Data Regions for Platform and Infrastructure Services.
Required IAM Policy
Each service in Oracle Cloud Infrastructure integrates with Identity and Access Management for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API). For more information, see IAM Overview
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, and so on. 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 MySQL Database Service, see Policy Details for MySQL Database Service .
Block Volume Storage Encryption
MySQL Database Service uses Block Volume for all data storage. Block volumes are always encrypted. For more information, see Block Volume Encryption.
Limits on MySQL Database Service
See Service Limits for a list of applicable limits and instructions for requesting a limit increase.
MySQL Database and Audit Service
MySQL Database integrates with the Oracle Cloud Infrastructure Audit Service. For more information on how to use Audit, see Viewing Audit Events
MySQL Database Versions and Storage Engines
MySQL Database Service supports MySQL Enterprise Edition version 8.0 with InnoDB Storage Engine.
Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
MySQL Database Service has daily automatic backups and is resilient to failures because it leverages the Block Volumes to store user data. Consequently, it offers the same durability, security, and performance guarantees. However, the current generally available version of MySQL Database Service does not support multi-node synchronous replicas. Deployments with high uptime requirements and low data loss tolerance should consider that some events incur downtime or potential data loss.
The following table describes the Recovery Time Objective (downtime tolerance) and Recovery Point Objective (data loss tolerance) for the current MySQL Database Service version.
Table 1-1 RTO (downtime tolerance) and RPO (data loss tolerance) for the current MySQL Database Service
|Failure and Maintenance Events||Downtime (RTO)||Potential Data Loss (RPO)|
|Localized events, including:
||Minutes to hours||Near-zero|
|Events requiring restoring from backup because a synchronous replica does not exist, including:
||Minutes to hours||Up to the last successful automatic backup (scheduled every 24 hours)|
Automatic and manual backups are replicated to another availability domain and can be restored in the event of a disaster. Data loss is limited by the last successful backup.
HeatWave is an add-on to MySQL Database Service. It provides a highly performant and scalable in-memory analytic processing engine optimized for Oracle Cloud Infrastructure. Customers can run HeatWave on data stored in the MySQL database without requiring ETL and without any change to the application. Applications simply access HeatWave via standard MySQL protocols, and the typical administration actions are automated, integrated and accessible via the OCI Web Console, REST API, CLI, or DevOps tools. HeatWave queries achieve orders of magnitude acceleration over the MySQL database.
For more information, see HeatWave.