Oracle Autonomous Databases BYOL Summary Report

IT Asset Management (Cloud)
The Oracle Autonomous Databases BYOL Summary report gives you full visibility of Oracle Autonomous Databases running on Oracle Database@Azure using the bring your own license (BYOL) licensing model, and key data fields to help understand base configuration (size), and whether auto scaling is enabled for all BYOL instances.
Note: Oracle Autonomous Databases using the pay as you go (PAYG) license model are not displayed in this report.

Each record in the report represents an Oracle Autonomous Database instance running on Oracle Database@Azure. Oracle Database@Azure is an Oracle database service that runs on Oracle Cloud Infrastructure (OCI), and is remotely hosted on a Microsoft data center.

In addition, the report returns data to determine if an Oracle Real Application Clusters (RAC) license is required, and if Autonomous Data Guard (ADG) has been deployed. If an Oracle Autonomous Database is larger than 16 OCPUs, then an Oracle RAC license is required. If ADG has been deployed, an Active Data Guard license is also required.

Generating the report

  1. Go to the Oracle Autonomous Databases BYOL Summary page.
  2. Click Run report to display the results for all Oracle Autonomous Databases using the bring your own license (BYOL) licensing model running on Oracle Database@Azure deployments.

Reading the report

The following columns (listed alphabetically) are available.

Column name Description
Autoscaling

Shows whether Auto Scaling is enabled. Values can be TRUE or FALSE.
BYOL edition The BYOL license edition—Enterprise, Standard and so on.
BYOL limit The total number of BYOL licenses that can be consumed by this Oracle Autonomous Database instance.
Compute count

The total number of ECPUs/OCPUs that have been activated for this Oracle database license. You are charged for the number of compute cores (OCPUs, ECPUs) consumed.
Compute model

The pricing metric for Oracle Autonomous Databases. This value can be ECPU or OCPU. ECPU is based on the number of cores per hour elastically allocated from a pool of compute and storage servers. OCPU is defined as the equivalent of one physical core with hyper-threading enabled.
Database license The license from which the Oracle Autonomous Database instance in this row is consuming for their installations of Oracle software.
DB instance name
The name of the Oracle database instance, for example orcl. If the database is a container (or root) database which contains one or more pluggable databases, then the value which displays here is concatenated <instance name>~CDB_ROOT. For example, if the container database instance is orcl, then the container database displays as orcl~CDB_ROOT. Continuing with this example, if the pluggable databases within this container database are named MPDB1, MPDB2, MPDB3 and PDBORCL, then each would be listed as orcl~MPDB1, orcl~MPDB2, orcl~MPDB3, and orcl~PDBORCL respectively. Database instance names will only display when they satisfy the following conditions:
  • They link to a license where they are not supplementary applications and counted for consumption
  • They link to a license from which they or their device (Including VM Ware/Hyper V) consume a license
  • They are not on ignored devices
  • They are installed and in use.
DB instance version The version number of the Oracle Autonomous Database instance.
Hosted in

Shows the Oracle database service that this Oracle Autonomous Database instance is hosted on. For example—Oracle Cloud@Customer, Oracle Cloud Infrastructure and so on.
Instance role

Specifies the role assigned to the Oracle Autonomous Database instance.

Possible roles include:

  • None — Indicates that no role has been assigned.

  • Backup — Specifies that the Oracle Autonomous Database instance is being used as a backup database.

  • Failover — Specifies that the Oracle Autonomous Database instance is being used as a failover resource. The failover database is automatically transitioned to primary when the primary database fails. A database license includes right to run the licensed program(s) on an unlicensed spare computer in a failover environment for up to a total of ten separate days in any given calendar year.
  • Mirroring — Specifies that the Oracle Autonomous Database instance is being used to mirror another Oracle Autonomous Database instance.
  • Standby — Specifies that the Oracle Autonomous Database instance is being used as a standby database. The standby database has to be manually transitioned to primary in the events like planned maintenance of the primary database.
  • Other — Specifies that the device is being used for any other purpose that the above-specified options.
  • Primary — Specifies that the Oracle Autonomous Database instance is actively processing the user transactions.
Inventory date

The date when the most recent inventory information was collected for this Oracle Autonomous Database.
Option ADG in use Shows if Autonomous Data Guard (ADG) has been deployed. If ADG has been deployed, an Active Data Guard license is required.
Option RAC in use Shows if an Oracle Real Application Clusters (RAC) license is currently in use. If an Oracle Autonomous Database is larger than 16 OCPUs, then an Oracle RAC license is required.
Workload The Oracle data source type applicable to the Oracle Autonomous Database instance that can be integrated with Microsoft Azure. Values can be Oracle Autonomous Transaction Processing or Oracle Autonomous Data Warehouse.

IT Asset Management (Cloud)

Current