View and Update Your License and Oracle Database Edition on Autonomous Database (ECPU Compute Model)

Describes how to view and update your license type and Oracle Database Edition for Autonomous Database.

Note:

See View and Update Your License and Oracle Database Edition on Autonomous Database (OCPU Compute Model) if you are using the OCPU compute model.

The License type field on the Oracle Cloud Infrastructure Console Autonomous Database details page shows your license type and Oracle Database Edition. For example:

License type: Bring Your Own License (BYOL), Enterprise Edition

Perform the following prerequisite steps as necessary:

Open the Oracle Cloud Infrastructure Console by clicking the next to Oracle Cloud.
From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
On the Autonomous Databases page select an Autonomous Database from the links under the Display name column.

To view or change your license type or Oracle Database Edition:

On the Details page, from the More actions drop-down list, select Update license and Oracle Database edition.

On the Update license and Oracle Database edition page select a license option from the choices:

License included:

Subscribe to new database software licenses and the database cloud service.

When the workload type is JSON or APEX, license included is the only choice available.

Bring your own license (BYOL):

Select this option to bring existing database software licenses to the database cloud service when your organization already owns Oracle database software licenses.

When you select Bring your own license (BYOL) you also specify the Oracle Database Edition. The Oracle Database Edition you specify is based on the licenses you bring to Autonomous Database and determines the values that you can select for the ECPU count.

Choose one of: Oracle Database Enterprise Edition (EE) or Oracle Database Standard Edition (SE).

Oracle Database Edition	Description
Oracle Database Enterprise Edition (EE)	You have two options, depending on whether you select Enable the BYOL ECPU limit and set the number of ECPUs to be covered by BYOL (we call this the BYOL ECPU limit option and this option is either selected or deselected): BYOL ECPU limit selected: When you select this option you set a BYOL ECPU limit for your BYOL licenses and any usage beyond the BYOL ECPU limit is billed as License included usage. The value you specify indicates how many licenses to use from your existing Enterprise Edition licenses. That is, the BYOL ECPU limit indicates how many of your existing licenses you are bringing to the Autonomous Database instance. The BYOL ECPU limit you specify indicates how many ECPUs will be covered by the Enterprise Edition licenses you bring. Any ECPU usage beyond the BYOL ECPU limit will not by covered as BYOL, and is billed as License Included usage. BYOL ECPU limit deselected: For this license type the maximum allowed value for ECPU count is 512, however you may contact your Oracle account team to request more ECPUs. With compute auto scaling enabled you can use up to ECPU count x 3 ECPUs. For example, if you set the ECPU count to 512, you can use up to 1,536 ECPUs.
Oracle Database Standard Edition (SE)	For this license type the maximum allowed value for ECPU count is 32. With compute auto scaling enabled you can use up to ECPU count x 3 ECPUs. This license restricts the number of ECPUs you can use to a maximum of 32 ECPUs, with or without compute auto scaling enabled.

Oracle Database Edition

Description

Oracle Database Enterprise Edition (EE)

You have two options, depending on whether you select Enable the BYOL ECPU limit and set the number of ECPUs to be covered by BYOL (we call this the BYOL ECPU limit option and this option is either selected or deselected):

BYOL ECPU limit selected:

When you select this option you set a BYOL ECPU limit for your BYOL licenses and any usage beyond the BYOL ECPU limit is billed as License included usage. The value you specify indicates how many licenses to use from your existing Enterprise Edition licenses. That is, the BYOL ECPU limit indicates how many of your existing licenses you are bringing to the Autonomous Database instance. The BYOL ECPU limit you specify indicates how many ECPUs will be covered by the Enterprise Edition licenses you bring. Any ECPU usage beyond the BYOL ECPU limit will not by covered as BYOL, and is billed as License Included usage.
BYOL ECPU limit deselected:

For this license type the maximum allowed value for ECPU count is 512, however you may contact your Oracle account team to request more ECPUs. With compute auto scaling enabled you can use up to ECPU count x 3 ECPUs. For example, if you set the ECPU count to 512, you can use up to 1,536 ECPUs.

Oracle Database Standard Edition (SE)

For this license type the maximum allowed value for ECPU count is 32. With compute auto scaling enabled you can use up to ECPU count x 3 ECPUs. This license restricts the number of ECPUs you can use to a maximum of 32 ECPUs, with or without compute auto scaling enabled.

Click Save.

While the system applies the changes, the lifecycle state changes to Updating. The database remains up and accessible, there is no downtime while the license type updates. When the operation completes the lifecycle state shows Available.

If you have not specified a complete license type, Autonomous Database instances created before the introduction of the Oracle Database Edition will see the following message on the Oracle Cloud Infrastructure Console:

Description of adb_license_message.png follows

Description of the illustration adb_license_message.png

To dismiss this message, click Update license and Oracle Database edition and set a license type and Oracle Database Edition.

For information on Bring your own license (BYOL) and other licensing options for Oracle Cloud Infrastructure, see the following:

Lower your TCO for Oracle Database Standard Edition with the Bring Your Own License (BYOL) program
For BYOL policies, see Oracle Cloud Services contracts. BYOL policies are described in the Oracle PaaS and IaaS Universal Credits Service Descriptions document under Cloud Service Descriptions.
Frequently asked questions: Oracle Bring Your Own License (BYOL)
Cloud pricing

Notes for performing Update license and Oracle Database edition operation:

If you try to switch to License type: Bring your own license (BYOL) Standard Edition when the base ECPU count is above 32, you see the following message:
You cannot select Oracle Database Standard Edition unless your ECPU count is a total of sixteen (32) or less ECPUs. Use the Manage Scaling option to adjust your ECPU count before changing to Standard Edition.

In this case, lower your ECPU count before you change the license type. See Remove CPU or Storage Resources or Disable Auto Scaling for more information.
If you switch to License type: Bring your own license (BYOL) Standard Edition when the base ECPU count is 32 and compute auto scaling is enabled, you see the following message:
Compute auto scaling will be disabled with a base ECPU count of 32, under an Oracle Database Standard Edition license.

In this case, Compute auto scaling is disabled and the ECPU count is set to 32.
If you switch to License type: Bring your own license (BYOL) Standard Edition when the base ECPU count is below 32 and above 8, with compute auto scaling enabled, you see the following message:
Your compute auto scaling maximum will be set to 32 ECPUs, under an Oracle Database Standard Edition license.

In this case, the maximum number of ECPUs with compute auto scaling is 32.
See Elastic Pool Notes for information on BYOL usage with an instance that is in an elastic pool.
The BYOL ECPU limit you set on an Autonomous Data Guard Primary database does not apply to a cross-region or cross-tenancy Autonomous Data Guard Standby database. On a cross-region or cross-tenancy Standby you can independently set the BYOL ECPU limit, as required.

See Autonomous Data Guard Notes for information on BYOL usage with Autonomous Data Guard.
For information on Bring your own license (BYOL) and other licensing options for Oracle Cloud Infrastructure, see the following:
- Lower your TCO for Oracle Database Standard Edition with the Bring Your Own License (BYOL) program
- For BYOL policies, see Oracle Cloud Services contracts. BYOL policies are described in the Oracle PaaS and IaaS Universal Credits Service Descriptions document under Cloud Service Descriptions.
- Frequently asked questions: Oracle Bring Your Own License (BYOL)
- Cloud pricing

Parent topic: Update Billing Model, License Type, or Update Instance to a Paid Instance