BOM and SKUs for autonomous databases

There are two components to Autonomous Databases:

• Infrastructure component: You need to subscribe to Exadata Cloud Infrastructure for an OCI deployment or ExaC@C infrastructure for a C@C deployment.
• Database OCPUs: Subscribe hourly per active OCPU consumed, using either License Included or the BYOL type. Billing happens monthly at an aggregate level, a total of all active OCPUs, for each Exadata Cloud Infrastructure resource.

There are two scenarios possible in terms of licensing: existing Oracle customers may have already invested in Oracle databases and options. Oracle provides flexibility to use BYOL while provisioning an Autonomous Database in the Oracle cloud. This option brings down the service cost significantly. The other option is the License Included service deployment where customers do not own prior licenses of Oracle databases.

Note

If you are using BYOL, it is feasible to consistently change from 16 or fewer OCPUs to more than 16 OCPUs. The main prerequisite is that your BYOL should incorporate RAC when scaling past 16 OCPUs. For the most accurate policies and the latest information, you should check Oracle’s site.

ADB-D on OCI pricing details can be found on the ADB pricing pages. ADB on ExaC@C pricing details can be found on Oracle’s website under the Pricing information page:

• https://www.oracle.com/autonomous-database/
• https://www.oracle.com/autonomous-database/autonomous-transaction-processing/pricing/
• https://www.oracle.com/autonomous-database/autonomous-data-warehouse/pricing/

On OCI, the license type is defined at the Exadata infrastructure level. On ExaC@C, this is defined at the Autonomous VM cluster level. As of today, you can only use one license type (License Included or BYOL) on an Exadata rack until multiple VM clusters per rack are supported on ADB-D and ADB-ExaC@C, respectively.