Introduction to Autonomous Database on Exadata Cloud@Customer

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.

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.
    • 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.

Deployment Order

You must create the dedicated Exadata infrastructure resources in the following order:

  1. Exadata Infrastructure. For more information, see Preparing for Exadata Cloud@Customer and Provisioning Exadata Cloud@Customer System.
  2. Autonomous Exadata VM cluster. For more information, see Managing Autonomous Exadata VM Clusters.
  3. Autonomous Container Database. For more information, see Managing Autonomous Container Databases.
  4. Autonomous Database. For more information, see Managing Autonomous Databases.

User Roles

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

Resource Limits

The following tables list the resource limits, both enforced and recommended for dedicated Autonomous Database deployments on Oracle Cloud and Exadata Cloud@Customer.

Note

The limits listed in the following tables apply to all the Exadata Systems supported by a dedicated Autonomous Database. Exceptions (if any) are highlighted accordingly.

Table 6-1 Enforced Resource Limits (Maximum)

Resource Quarter Rack Half Rack Full Rack
Autonomous Databases 1000

(920 on Exadata X7 system)

2000

(1840 on Exadata X7 system)

4000

(3680 on Exadata X7 system)

Autonomous Container Databases 12 12 12

Table 6-2 Recommended Resource Limits (Maximum)

Resource Quarter Rack Half Rack Full Rack
Autonomous Databases per Autonomous Container Database 200 200 200
Autonomous Databases per Autonomous Container Database with Autonomous Data Guard Configured 25 25 25
Note

It is possible to provision more Autonomous Databases than those recommended in the Recommended Resource Limits table, especially with fractional OCPUs. 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 dedicated Autonomous Database deployments, see Availability Service Level Objectives (SLOs).

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-3 Oracle Exadata Cloud@Customer X9M-2 System Specifications

Specification Exadata X9M-2 Quarter Rack Exadata X9M-2 Half Rack Exadata X9M-2 Full Rack
Number of Compute Nodes 2 4 8
Total Maximum Number of Enabled CPU Cores 124 248 496
Total RAM Capacity 2780 GB 5560 GB 11120 GB
Total Persistent Memory Capacity 4.5 TB 9.0 TB 18.0 TB
Number of Exadata Storage Servers 3 6 12
Maximum Database Size, No Local Backup 153 TB 307 TB 615 TB
Maximum Database Size, Local Backup (Exadata Cloud@Customer only) 76 TB 153 TB 307 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-4 Oracle Exadata Cloud@Customer X8M-2 System Specifications

Specification Exadata X8M-2 Quarter Rack Exadata X8M-2 Half Rack Exadata X8M-2 Full Rack
Number of Compute Nodes 2 4 8
Total Maximum Number of Enabled CPU Cores 100 200 400
Total RAM Capacity 2780 GB 5560 GB 11120 GB
Persistent Memory 4.5 TB 9.0 TB 18.0 TB
Number of Exadata Storage Servers 3 6 12
Maximum Database Size, No Local Backup 119 TB 239 TB 479 TB
Maximum Database Size, Local Backup (Exadata Cloud@Customer only) 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-5 Oracle Exadata Cloud@Customer X8-2 System Specifications

Specification Exadata X8-2 Quarter Rack Exadata X8-2 Half Rack Exadata X8-2 Full Rack
Shape Name Exadata.Quarter3.100 Exadata.Half3.200 Exadata.Full3.400
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
Maximum Database Size, No Local Backup 119 TB 238 TB 476 TB
Maximum Database Size, Local Backup (Exadata Cloud@Customer only) 59 TB 119 TB 239 TB

Access Control Lists (ACLs) for Autonomous Databases on Exadata Cloud@Customer

An access control list (ACL) provides additional protection to your database by allowing only the clients with specific IP addresses to connect to the database. You can add IP addresses individually, or in CIDR blocks.

You can optionally create an ACL during database provisioning, or at any time thereafter. You can also edit an ACL at any time. Enabling an access control list with an empty list of IP addresses makes the database inaccessible. For more information, see "Manage Access Control List of an Autonomous Database".

Note the following about using an ACL with your Autonomous Database:

  • The Autonomous Database Service console is not subject to ACL rules.
  • Oracle Application Express (APEX), RESTful services, and SQL Developer Web are not subject to ACLs. Choosing to enable an ACL disables these features automatically.
  • Performance Hub is not subject to ACL rules.
  • While creating a database, if setting ACL fails, then provisioning the database also fails.
  • Updating ACL is allowed if the database is in Available and AvailableNeedsAttention states.
  • Restoring a database does not overwrite the existing ACLs.
  • Cloning a database, full and metadata, will have the same access control settings as the source database. You can make changes as necessary.
  • All CDB operations are allowed during ACL update. However, ADB operations are not allowed during ACL update.