Oracle Autonomous Database on Oracle 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 Oracle 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.
Database System Architecture Overview
Oracle Autonomous Database on Oracle Exadata Cloud@Customer has a four-level database architecture model that makes use of Oracle multitenant database architecture.
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.
- Oracle Exadata Cloud@Customer infrastructure cannot simultaneously have both Autonomous and Exadata VM clusters.
Autonomous VM clusters on 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 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.
You must create the dedicated Exadata infrastructure resources in the following order:
- Exadata Infrastructure. See Preparing for Exadata Cloud@Customer and Provisioning Exadata Cloud@Customer Systems for more information.
- Autonomous Exadata VM cluster. See Managing Autonomous Exadata VM Clusters for more information.
- Autonomous Container Database. See Managing Autonomous Container Databases for more information.
- Autonomous Database. See Managing Autonomous Databases for more information.
Your organization may choose to split the administration of the Oracle Autonomous Database on Oracle 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 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
Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports the following shapes of Exadata Infrastructure resources.
The following table lists the Exadata Infrastructure resource shapes that Oracle Autonomous Database on Oracle Exadata Cloud@Customer supports.
|Specification||Exadata X8-2 Quarter Rack||Exadata X8-2 Half Rack||Exadata X8-2 Full Rack|
|Number of Compute Nodes||2||4||8|
|Total Maximum Number of Enabled CPU Cores||100||200||400|
|Total RAM Capacity||1440 GB||2880 GB||5760 GB|
|Number of Exadata Storage Servers||3||6||12|
|Total Raw Flash Storage Capacity||76.8 TB||153.6 TB||307.2 TB|
|Total Usable Storage Capacity||149.7 TB||299.4 TB||598.7 TB|
|Maximum Number of Autonomous Container Databases||12 (See note)||12 (See note)||12 (See note)|
|Maximum Number of Autonomous Databases per Autonomous Container Database||100 (See note)||200 (See note)||400 (See note)|
Oracle Autonomous Database does not currently support over-provisioning, the ability for multiple autonomous databases to share a single CPU core. Therefore, an Exadata Infrastructure resource can currently support, across all its autonomous container databases, up to as many autonomous databases as it has CPU cores.