Introduction to Autonomous Database on Exadata Cloud@Customer
Oracle Autonomous Database on Exadata Cloud@Customer combines the benefits of a self-driving, self-securing, and self-repairing database management system and the security and control offered by having it deployed securely on-premise behind your firewall.
After purchasing Autonomous Database on Exadata Cloud@Customer and creating, provisioning and activating its Exadata Infrastructure hardware and Oracle Cloud resource, several additional resource types become available in the Exadata Cloud@Customer section of the Oracle Cloud Infrastructure console: Autonomous Exadata VM Clusters, Autonomous Container Databases and Autonomous Databases. You use these resources to create and manage your secure, on-premise deployment of Oracle Autonomous Database.
Parent topic: Autonomous Database on Exadata Cloud@Customer
Database System Architecture Overview
Autonomous Database on Exadata Cloud@Customer has a four-level database architecture model that makes use of Oracle multitenant database architecture.
Resource Types
Each level of the architecture model corresponds to one of the following resources types:
-
Oracle Exadata Cloud@Customer infrastructure: Hardware rack that includes compute nodes and storage servers, tied together by a high-speed, low-latency InfiniBand network and intelligent Exadata software.
Oracle Exadata Cloud@Customer infrastructure is common for both Autonomous and Non-Autonomous resources.
For a list of the hardware and Oracle Cloud resource characteristics of Oracle Exadata Cloud@Customer infrastructure resources that support Autonomous Databases, see Available Exadata Infrastructure Hardware Shapes.
- Only the Oracle Exadata Cloud@Customer infrastructures deployed before Oracle announced support for Autonomous Databases on Oracle Exadata Cloud@Customer do not support Autonomous resources listed below. Please contact your Oracle sales representative to understand the infrastructure upgrades required for supporting Oracle Autonomous Databases.
- You can create only one Autonomous VM cluster in an Exadata Infrastructure.
-
Autonomous VM clusters on Oracle Exadata Cloud@Customer infrastructure: VM cluster is a set of symmetrical VMs across all Compute nodes. Autonomous Container and Database run all the VMs across all nodes enabling high availability. It consumes all the resources of the underlying Exadata Infrastructure.
Before you can create any Autonomous Databases on your Oracle Exadata Cloud@Customer infrastructure, you must create an Autonomous VM cluster network, and you must associate it with a VM cluster.
-
Autonomous Container Database: Provides a container for multiple Autonomous Databases.
- Autonomous Database: You can create multiple autonomous databases within the same autonomous container database. You can configure Oracle Autonomous Database for either transaction processing or data warehouse workloads.
Related Topics
Parent topic: Database System Architecture Overview
Deployment Order
You must create the dedicated Exadata infrastructure resources in the following order:
- Exadata Infrastructure. For more information, see Preparing for Exadata Cloud@Customer and Provisioning Exadata Cloud@Customer System.
- Autonomous Exadata VM cluster. For more information, see Managing Autonomous Exadata VM Clusters.
- Autonomous Container Database. For more information, see Managing Autonomous Container Databases.
- Autonomous Database. For more information, see Managing Autonomous Databases.
Related Topics
Parent topic: Database System Architecture Overview
User Roles
Your organization may choose to split the administration of the Autonomous Database on Exadata Cloud@Customer into the following roles:
-
Fleet Administrator: Fleet administrators create, monitor and manage Autonomous Exadata Infrastructure and Autonomous Container Database resources. They must also setup customer managed Backup Destinations, such as Recovery Appliance and NFS to be used by Autonomous Databases. A fleet administrator must have permissions for using the networking resources required by the Oracle Exadata Database Service on Cloud@Customer infrastructure, and permissions to manage the infrastructure and container database resources.
-
Database Administrator: Database administrators create, monitor and manage Autonomous Databases. They also create and manage users within the database. Database administrators must have permissions for using container databases, for managing autonomous databases and backups, and for using the related networking resources. At the time of provisioning an Autonomous Database, the administrator provides user credentials for the automatically created ADMIN account, which provides administrative rights to the new database.
- Database User: Database users are the developers who write applications that connect to and use an Autonomous Database to store and access the data. Database users do not need Oracle Cloud Infrastructure accounts. They gain network connectivity to and connection authorization information for the database from the database administrator.
Available Exadata Infrastructure Hardware Shapes
Resource Limits
The following table lists the resource limits for Autonomous Database on Dedicated Exadata Infrastructure deployments on Oracle Public Cloud and Exadata Cloud@Customer.
Resource Limits (Maximum)
-
The number of Provisioned CPUs determines the maximum number of Autonomous Databases that you can create. The smallest Autonomous Database can be created with 0.1 CPUs. Therefore the maximum number of Autonomous Databases that can be created is ten times the amount of Provisioned CPUs.
For example, an X9M Quarter Rack system with 252 Provisioned OCPUs allows a maximum of 2520 Autonomous Databases.
- The maximum number of Autonomous Container Databases per Autonomous Exadata VM Cluster (AVMC) is 16.
Recommended Resource Limits (Maximum)
Table 6-2 Recommended Resource Limits (Maximum)
| Resource | Recommended Limit |
|---|---|
| Autonomous Databases per Autonomous Container Database | 200 |
| Autonomous Databases per Autonomous Container Database with Autonomous Data Guard Configured | 25 |
It is possible to provision more Autonomous Databases than those mentioned in the above recommended limits table, especially with CPU overprovisioning. However, this implies compromising the Service Level Objectives (SLOs) to return an application online following an unplanned outage or a planned maintenance activity. To know the SLO details for Autonomous Database on Dedicated Exadata Infrastructure deployments, see Availability Service Level Objectives (SLOs).
Limits for Autonomous Exadata VM Clusters
You can create multiple Autonomous Exadata VM Clusters (AVMCs) on an Exadata Infrastructure resource. There are no hard limits on the number of AVMCs or Autonomous Container Databases (ACDs) you can provision on your Exadata Infrastructure. The AVMCs and ACDs have a minimum resource requirement, and you can create them as long as the minimum amount of resources is available.
To create an Autonomous Exadata VM Cluster, the minimum resources required are 40 ECPUs or 10 OCPUs per node, 120 GB Memory per node, 338.5 GB Local Storage per node, and 6.61 TB Exadata Storage. Similarly, the minimum resources needed per node to create an ACD are 8 ECPUs or 2 OCPUs and 50 GB Local Storage. As long as your Exadata Infrastructure has these minimum resources available, an AVMC and ACD can be created.
Exadata System Shapes
Autonomous Database on Dedicated Exadata Infrastructure is offered in the following Exadata System Shapes:
- Base System: Contains two database servers and three Oracle Exadata Storage Servers. A Base System is an entry-level configuration. Compared to other configurations, a Base System contains Oracle Exadata Storage Servers with significantly less storage capacity, and database servers with significantly less memory and processing power.
- Quarter Rack: Contains two database servers and three Oracle Exadata Storage Servers.
- Half Rack: Contains four database servers and six Oracle Exadata Storage Servers.
- Full Rack: Contains eight database servers and 12 Oracle Exadata Storage Servers.
- X10M: Starts with two standard memory (1390 GB) database servers and three Oracle Exadata Storage Servers, and can be expanded up to a maximum of 32 database servers and 64 storage servers.
- X10M-Large: Starts with two large memory (2090 GB) database servers and three Oracle Exadata Storage Servers, and can be expanded up to 32 large memory database servers and 64 storage servers.
- X10M-Extra Large: Starts with two large memory (2800 GB) database servers and three Oracle Exadata Storage Servers, and can be expanded up to 32 large memory database servers and 64 storage servers.
Each Exadata System Shape is equipped with a fixed amount of memory, storage, and network resources. All Shapes are based on Oracle Exadata X10M, X9M-2, X8M-2, X8-2, or X7-2 System Models.
Oracle Exadata X10M System Model Specifications
Review the technical specifications of X10M system model.
Table 6-3 Oracle Exadata Cloud@Customer X10M System Specifications
| Specification | Quarter Rack X10M (min config) | Quarter Rack X10M-L (min config) | Quarter Rack X10M-XL (min config) |
|---|---|---|---|
| Minimum Number of X10M DB servers | 2 | 2 | 2 |
| Minimum Number of X10M Storage Servers | 3 | 3 | 3 |
| Total Number of Usable DB node OCPUs (assuming 2 cores per host) | 380 | 380 | 380 |
| Total Memory Available for VMs (GB) | 2780 | 4180 | 5600 |
| Max /u02 capacity (GB) per VM | 900 | 900 | 900 |
| VM Image overhead per VM (GB) | 184 | 184 | 184 |
| Max local storage (/u02 + VM Image capacity) (GB) per infrastructure | 2243 | 2243 | 2243 |
| Total number of VM clusters* | 8 | 8 | 8 |
| Minimum CPUs per VM | 2 | 2 | 2 |
| Minimum memory per VM (GB) | 30 | 30 | 30 |
| Min Local File System Storage per VM (GB) | 60 | 60 | 60 |
| Min Exadata Storage per VM Cluster | 2 TB | 2 TB | 2 TB |
| Total Usable ASM storage capacity (TB) per Cell | 80 TB | 80 TB | 80 TB |
| Exadata RMDA Memory (XRMEM) | 1.25 TB per storage server | 1.25 TB per storage server | 1.25 TB per storage server |
* A maximum of 16 clusters can be created on a single system.
Oracle Exadata X9M-2 System Model Specifications
The following table lists the Exadata Infrastructure resource shapes that Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports.
Table 6-4 Oracle Exadata Cloud@Customer X9M-2 System Specifications
| Specification | Exadata X9M-2 Base Rack | Exadata X9M-2 Quarter Rack | Exadata X9M-2 Half Rack | Exadata X9M-2 Full Rack |
|---|---|---|---|---|
| Number of Compute Nodes | 2 | 2 | 4 | 8 |
| Total Maximum Number of Enabled CPU Cores | 48 | 124 | 248 | 496 |
| Total RAM Capacity | 656 GB | 2780 GB | 5560 GB | 11120 GB |
| Total Persistent Memory Capacity | 0 | 4.5 TB | 9.0 TB | 18.0 TB |
| Number of Exadata Storage Servers | 3 | 3 | 6 | 12 |
| Maximum Database Size, No Local Backup | 59 TB | 152 TB | 305 TB | 610 TB |
| Maximum Database Size, Local Backup (Exadata Cloud@Customer only) | 29 TB | 76 TB | 152 TB | 305 TB |
For more information, see Oracle Exadata Database Service on Exadata Cloud@Customer X9M datasheet.
Oracle Exadata X8M-2 System Model Specifications
The following table lists the Exadata Infrastructure resource shapes that Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports.
Table 6-5 Oracle Exadata Cloud@Customer X8M-2 System Specifications
| Specification | X8M-2 Base Rack | Exadata X8M-2 Quarter Rack | Exadata X8M-2 Half Rack | Exadata X8M-2 Full Rack |
|---|---|---|---|---|
| Number of Compute Nodes | 2 | 2 | 4 | 8 |
| Total Maximum Number of Enabled CPU Cores | 48 | 100 | 200 | 400 |
| Total RAM Capacity | 656 GB | 2780 GB | 5560 GB | 11120 GB |
| Persistent Memory | 0 | 4.5 TB | 9.0 TB | 18.0 TB |
| Number of Exadata Storage Servers | 3 | 3 | 6 | 12 |
| Maximum Database Size, No Local Backup | 59 TB | 119 TB | 239 TB | 479 TB |
| Maximum Database Size, Local Backup (Exadata Cloud@Customer only) | 29 TB | 59 TB | 119 TB | 239 TB |
Oracle Exadata X8-2 System Model Specifications
The following table lists the Exadata Infrastructure resource shapes that Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports.
Table 6-6 Oracle Exadata Cloud@Customer X8-2 System Specifications
| Specification | Exadata X8-2 Base Rack | Exadata X8-2 Quarter Rack | Exadata X8-2 Half Rack | Exadata X8-2 Full Rack |
|---|---|---|---|---|
| Shape Name | Exadata.Base3.48 | Exadata.Quarter3.100 | Exadata.Half3.200 | Exadata.Full3.400 |
| Number of Compute Nodes | 2 | 2 | 4 | 8 |
| Total Maximum Number of Enabled CPU Cores | 48 | 100 | 200 | 400 |
| Total RAM Capacity | 720 GB | 1440 GB | 2880 GB | 5760 GB |
| Number of Exadata Storage Servers | 3 | 3 | 6 | 12 |
| Maximum Database Size, No Local Backup | 59 TB | 119 TB | 238 TB | 476 TB |
| Maximum Database Size, Local Backup (Exadata Cloud@Customer only) | 29 TB | 59 TB | 119 TB | 239 TB |
Oracle Exadata X7-2 System Model Specifications
The following table lists the Exadata Infrastructure resource shapes that Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports.
Table 6-7 Oracle Exadata Cloud@Customer X7-2 System Specifications
| Specification | Exadata X7-2 Base Rack | Exadata X7-2 Quarter Rack | Exadata X7-2 Half Rack | Exadata X7-2 Full Rack |
|---|---|---|---|---|
| Shape Name | Exadata.Base2.44 | Exadata.Quarter2.92 | Exadata.Half2.184 | Exadata.Full2.368 |
| Number of Compute Nodes | 2 | 2 | 4 | 8 |
| Total Maximum Number of Enabled CPU Cores | 44 | 92 | 184 | 368 |
| Total RAM Capacity | 480 GB | 1440 GB | 2880 GB | 5760 GB |
| Number of Exadata Storage Servers | 3 | 3 | 6 | 12 |
| Maximum Database Size, No Local Backup | 59 TB | 85.5 TB | 171.1 TB | 342.1 TB |
| Maximum Database Size, Local Backup (Exadata Cloud@Customer only) | 29 TB | 42.8 TB | 85.5 TB | 171.1 TB |