Chapter 1

How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
ECPU usage Autonomous B99708 ECPU per hour 1 ECPU Cost report: in the
(License JSON Database Minimum number product/
Included) – ECPU of ECPUs is 2 Description
column, find,
"Autonomous
JSON Database
– ECPU"
Usage report: in
the product/
resource
column, find
PIC_AJD_ECPU_
LI
Database Oracle B95706 Gigabyte Storage 1 GB Cost report: in the
Storage usage Autonomous Capacity Per Minimum storage product/
Database Month size is 20 GB Description
Storage for column, find,
Transaction "Oracle
Processing Autonomous
Database
Storage for
Transaction
Processing"
Usage report: in
the product/
resource
column, find
PIC_ADB_STORA
GE_ATP
Backup Storage Oracle B95754 Gigabyte Storage 1 GB Cost report: in the
usage Autonomous Capacity Per Backups are product/
Database Month billed per GB Description
Storage column, find,
"Database
Backup Storage"
Usage report: in
the product/
resource
column, find
PIC_ADB_STORA
GE

See Cost and Usage Reports Overview for details on the cost and usage reports.

Billing Information: APEX Service ECPU Compute Model

Shows billing information for APEX Service with the ECPU compute model.

1-35
 Chapter 1
How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
ECPU usage APEX Service – B99709 ECPU per hour 1 ECPU Cost report: in the
(License ECPU Minimum number product/
Included) of ECPUs is 2 Description
column, find,
"APEX Service –
ECPU"
Usage report: in
the product/
resource
column, find
PIC_APEX_ECPU
_LI
Database Oracle B95706 Gigabyte Storage 1 GB Cost report: in the
Storage usage Autonomous Capacity Per Minimum storage product/
Database Month size is 20 GB Description
Storage for column, find,
Transaction "Oracle
Processing Autonomous
Database
Storage for
Transaction
Processing"
Usage report: in
the product/
resource
column, find
PIC_ADB_STORA
GE_ATP
Backup Storage Oracle B95754 Gigabyte Storage 1 GB Cost report: in the
usage Autonomous Capacity Per Backups are product/
Database Month billed per GB Description
Storage column, find,
"Database
Backup Storage"
Usage report: in
the product/
resource
column, find
PIC_ADB_STORA
GE

See Cost and Usage Reports Overview for details on the cost and usage reports.

OCPU Compute Model Billing Information

Provides billing information for Autonomous Transaction Processing, Autonomous
Data Warehouse, Autonomous JSON Database, and APEX Service with the OCPU
compute model.

1-36
 Chapter 1
How Is Autonomous Database Billed?

Note:
OCPU is a legacy billing metric and has been retired for Autonomous Data
Warehouse (Data Warehouse workload type) and Autonomous Transaction
Processing (Transaction Processing workload type). Oracle recommends using
ECPUs for all new and existing Autonomous Database deployments. See Oracle
Support Document 2998742.1 for more information.

• Billing Information: Autonomous Transaction Processing OCPU Compute Model

• Billing Information: Autonomous Data Warehouse OCPU Compute Model
• Billing Information: Autonomous JSON Database OCPU Compute Model
• Billing Information: APEX Service OCPU Compute Model

Billing Information: Autonomous Transaction Processing OCPU Compute Model

Shows billing information for Autonomous Transaction Processing with the OCPU compute
model.

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
OCPU usage Oracle B90453 OCPU per hour 1 OCPU Cost report: In
(License Autonomous the product/
Included) Transaction Description
Processing column, find
"Oracle
Autonomous
Transaction
Processing"
Usage report: in
the product/
resource
column, find
PIC_ATP_COMPU
TE
OCPU usage Oracle B90454 OCPU per hour 1 OCPU Cost report: Cost
(Bring your own Autonomous report: in the
license) Transaction product/
Processing – Description
BYOL column, find,
"Oracle
Autonomous
Transaction
Processing –
BYOL"
Usage report: in
the product/
resourceID
column, find
PIC_ATP_COMPU
TE_BYOL

1-37
 Chapter 1
How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
Database Oracle B90455 Terabyte Storage 1 TB Cost report: in the
Storage usage Autonomous Capacity Per product/
Transaction Month Description
Processing - column, find,
Exadata Storage "Oracle
Autonomous
Transaction
Processing -
Exadata Storage"
Usage report: in
the product/
resource
column, find
PIC_ATP_EXADA
TA_STORAGE

See Cost and Usage Reports Overview for details on the cost and usage reports.

Billing Information: Autonomous Data Warehouse OCPU Compute Model

Shows billing information for Autonomous Data Warehouse with the OCPU compute
model.

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
OCPU usage Oracle B89040 OCPU per hour 1 OCPU Cost report: in the
(License Autonomous Data product/
Included) Warehouse Description
column, find
"Oracle
Autonomous Data
Warehouse"
Usage report: in
the product/
resource
column, find
PIC_ADWC_COMP
UTE

1-38
 Chapter 1
How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
OCPU usage Oracle B89039 OCPU per hour 1 OCPU Cost report: in the
(Bring your own Autonomous Data product/
license) Warehouse – Description
BYOL column, find
"Oracle
Autonomous Data
Warehouse –
BYOL"
Usage report: in
the product/
resource
column, find
PIC_ADWC_COMP
UTE_BYOL
Database Oracle B89041 Terabyte Storage 1 TB Cost report: in the
Storage usage Autonomous Data Capacity Per product/
Warehouse - Month Description
Exadata Storage column, find
"Oracle
Autonomous Data
Warehouse -
Exadata Storage"
Usage report: in
the product/
resource
column, find
PIC_ADWC_EXAD
ATA_STORAGE

See Cost and Usage Reports Overview for details on the cost and usage reports.

Billing Information: Autonomous JSON Database OCPU Compute Model

Shows billing information for Autonomous JSON Database with the OCPU compute model.

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
OCPU usage Oracle B92212 OCPU per hour 1 OCPU Cost report: in the
(License Autonomous product/
Included) JSON Database Description
column, find
"Oracle
Autonomous
JSON Database"
Usage report: in
the product/
resource
column, find
PIC_AJD_COMPU
TE

1-39
 Chapter 1
How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
Database Oracle B90453 Terabyte Storage 1 TB Cost report: in the
Storage usage Autonomous Capacity Per product/
Transaction Month Description
Processing - column, find
Exadata Storage "Oracle
Autonomous
JSON Database -
Exadata Storage"
Usage report: in
the product/
resource
column, find
PIC_ATP_EXADA
TA_STORAGE

Note:
In the OCPU model, 60 days of automatic backups are included in the cost of
database storage and have no additional charge. Long-term backups are
billed additionally, as database storage (Part Number: B90453).

See Cost and Usage Reports Overview for details on the cost and usage reports.

Billing Information: APEX Service OCPU Compute Model

Shows billing information for APEX Service with the OCPU compute model.

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
OCPU usage Oracle APEX B92911 OCPU per hour 1 OCPU Cost report: In
(License Application the product/
Included) Development Description
column, find
"Oracle APEX
Application
Development"
Usage report: in
the product/
resource
column, find
PIC_ADBS_APEX
_LI

1-40
 Chapter 1
How Is Autonomous Database Billed?

Resource SKU Name Part Number Metric Min. Increments Cost and Usage
Description Allowed Reports
Database Oracle B90453 Terabyte Storage 1 TB Cost report: in the
Storage usage Autonomous Capacity Per product/
Transaction Month Description
Processing - column, find,
Exadata Storage "Oracle
Autonomous
Transaction
Processing -
Exadata Storage"
Usage report: in
the product/
resource
column, find
PIC_ATP_EXADA
TA_STORAGE

Note:
In the OCPU model, 60 days of automatic backups are included in the cost of
database storage and have no additional charge. Long-term backups are billed
additionally, as database storage (Part Number: B90453).

See Cost and Usage Reports Overview for details on the cost and usage reports.

Oracle Autonomous Database Serverless Features Billing

Shows billing information for Autonomous Database features for ECPU and OCPU compute
models.

• ECPU Compute Model

• OCPU Compute Model

ECPU Compute Model

• Automatic Backups: The storage for backups is billed, per GB, in addition to your
selected database storage.
For example, if backups are occupying 200 GB of storage you are billed for 200 GB of
backup storage (in addition to the usage billed for your selected number of ECPUs and
database storage). See ECPU Compute Model Billing Information for more detail about
which SKUs are billed for backups.
• Long-Term Backups: The storage for long-term backups is billed, per GB, as backup
storage, in addition to your database storage.
For example, if automatic backups are currently occupying 200 GB and long-term
backups are occupying 600 GB of storage, you are billed for 800 GB of backup storage,
in addition to the usage billed for your selected ECPUs and database storage. See ECPU

1-41
 Chapter 1
How Is Autonomous Database Billed?

Compute Model Billing Information for more detail about which SKUs are billed for
each workload type and backups.
• Compute Auto-Scaling: When compute auto scaling is enabled, your database
may use and you may be billed for additional ECPU consumption as needed by
your workload, up to three times (3x) the number of base ECPUs, as shown in the
ECPU count on the Oracle Cloud Infrastructure Console.
– Your billed ECPU usage per hour while your database is running is based on
the base number of ECPUs you selected for your database, plus any
additional ECPU usage due to auto-scaling.
– A stopped Autonomous Database instance has zero ECPU usage.
– ECPU usage is measured each second, in units of whole ECPUs and
averaged across an hour. If your database is running for less than an hour or
auto-scales for only part of an hour, it is billed per second for the average
ECPU consumption, over the base ECPUs, during that hour. The minimum
ECPU consumption is one minute.
For example, if your database has ECPU count 4 with Compute auto scaling
enabled:
– Assume in hour one your database is Available for the entire hour and ECPU
utilization is below 4 ECPUs. Your database will be billed for 4 ECPUs.
– Assume in hour two your database is Available for the entire hour and ECPU
utilization is below 4 ECPUs for 30 minutes, 50% of the hour, and auto scales
to 8 ECPUs for 30 minutes (the other 50% of the hour). The usage for this
period, for billing, is 6 ECPUs (based on the average per-second ECPU usage
for hour two).
• Storage Auto-Scaling:
– For storage usage below your reserved base storage, you are billed based on
your base storage.
– After your allocated storage exceeds your reserved base storage, storage
usage is billed based on your allocated storage rounded up to the nearest TB,
in a given hour.
For example, if your reserved base storage is 4 TB, until your allocated storage
exceeds 4 TB of storage, you are billed based on your base storage (4 TB). After
you exceed 4 TB, storage is billed based on the allocated storage rounded up to
the nearest TB, in a given hour. In this example, if the allocated storage grows
over 4 TB in a given hour, say to 4.9 TB, you are billed for 5 TB of storage from
that hour onward.
If you then delete 1 TB of data, your allocated storage remains at 4.9 TB and you
are billed for 5 TB until you perform a shrink operation. When you perform a shrink
operation, may be able to shrink /reduce your allocated storage back to 3.9 TB.
After the shrink operation completes and your allocated storage (3.9 TB) is once
again below your reserved base storage (4 TB), you will once again be billed for
your reserved base storage of 4 TB. See Shrink Storage for more information.
• Autonomous Data Guard Standby – Local (Same-Region)
Local Autonomous Data Guard peer databases incur the additional cost of the
base ECPUs and the storage of the Primary database, including any auto-scaled
storage usage, billed on the Primary database itself. Auto-scaled ECPUs of the
Primary database are not billed for additionally on the local Autonomous Data

1-42
 Chapter 1
How Is Autonomous Database Billed?

Guard peer database. The number of base ECPUs is specified by the number of ECPUs
as shown in the ECPU count on the Oracle Cloud Infrastructure Console.
For example, if you enable a local Autonomous Data Guard peer on a source database
with:
– 2 (base) ECPUs with Compute auto-scaling enabled and are consuming about 4
ECPUs per hour
– 1 TB of (base) storage with storage auto-scaling, consuming a total of 2 TB of
database storage
For the local Autonomous Data Guard peer you are billed for an additional 2 ECPUs
(your base ECPU selection), plus an additional 2 TB of storage (that is, the same amount
of storage reserved for the source Primary with auto-scale, on the Primary database).
When the Primary database is stopped, neither the primary nor the peer database is
billed for ECPU.
• Autonomous Data Guard Standby – Remote (Cross-Region)
Autonomous Data Guard cross-region peer databases incur the additional cost of the
base ECPUs and twice (2x) the storage of the Primary database, including any auto-
scaled storage usage, billed on the remote peer database. Auto-scaled ECPUs of the
Primary are not billed for additionally on the remote peer database. The number of base
ECPUs is specified by the number of ECPUs as shown in the ECPU count on the Oracle
Cloud Infrastructure Console.
For example, if you enable a cross-region Autonomous Data Guard peer for a source
database with:
– 2 (base) ECPUs with Compute auto-scaling enabled and are consuming about 4
ECPUs per hour
– 1 TB of (base) storage with storage auto-scaling, consuming a total of 2 TB of
database storage
For the cross-region Autonomous Data Guard peer you are billed an additional 2 ECPUs
(your base ECPU selection), plus 4 TB of storage (that is 2x the storage reserved for the
source Primary with auto-scaling, billed on the remote peer database).
When the Primary database is stopped, neither the primary nor the peer database are
billed for ECPU.
• Backup-Based Disaster Recovery – Local (Same-Region) Backup Copies There are
no additional costs for local Backup-Based Disaster Recovery, other than the cost of
storage for automatic backups.
• Backup-Based Disaster Recovery – Remote (Cross-Region) Backup Copies Billing
for a cross-region Backup-Based Disaster Recovery is twice (2x) the amount of backup
storage required for the replicated cross-region backups, billed to the remote peer.
For example, if you enable a cross-region backup copy on a source database with:
– 2 (base) ECPUs
– 2 TB of database storage
If the backups replicated to the remote region take up 1.9 TB of storage, you will be billed
for 3.8 TB of backup storage on the remote backup copy peer database.
• Refreshable Clone Local (Same-Region) Local refreshable clones have their own
configurable ECPU selection, and so they are billed for ECPU based on the user-
selected number of ECPUs, with or without auto scaling; they do not get billed

1-43
 Chapter 1
How Is Autonomous Database Billed?

additionally over the ECPU selection. The number of ECPUs is specified by the
number of ECPUs as shown in the ECPU count on the Oracle Cloud
Infrastructure Console.
Local refreshable clones are billed for the same amount of storage as their source
database.
For example, if you create a 2 ECPU local refreshable clone from a source
database with:
– 4 ECPUs
– 1 TB of storage with storage auto-scaling and consuming 2 TB of storage
For the local refreshable clone you will be billed for 2 ECPUs, that is, the
refreshable clone's ECPU count value, and 2 TB of storage (that is, the storage
reserved for the source database).
When you start or stop the source database, your actions on the source database
do not affect the refreshable clone. A refreshable clone is started or stopped
independently of the source database.
• Refreshable Clone Remote (Cross-Region) Remote refreshable clones have
their own configurable ECPU selection, and so they are billed for ECPU based on
the user-selected ECPU (with or without auto scaling); they do not get billed
additionally over the ECPU selection. The number of ECPUs is specified by the
number of ECPUs as shown in the ECPU count on the Oracle Cloud
Infrastructure Console.
Remote refreshable clones are billed for twice (2x) the amount of storage as their
source database.
For example, if you create a 2 ECPU remote refreshable clone from a source
database with:
– 4 ECPUs
– 1 TB of storage with storage auto-scaling and consuming 2 TB of storage
For the remote refreshable clone you are billed for 2 ECPUs (that is, the
refreshable clone's ECPU selection) and 4 TB of storage (that is, 2x the storage
reserved for the source database)
Starting or stopping the source database does not affect the refreshable clone -
The refreshable clone can be started or stopped independently.
• Snapshot Standby for Remote (Cross-Region) Disaster Recovery
Snapshot standby ECPU usage is billed based on the base ECPU count and any
additional ECPU usage if compute auto-scaling is enabled. The number of base
ECPUs is specified by the number of ECPUs, as shown in the ECPU count on the
Oracle Cloud Infrastructure Console.
Snapshot standby storage usage is billed based on the storage of the snapshot
standby plus (1x) the storage of the source primary database.
For example, if you have a 2 ECPU and 3 TB snapshot standby from a source
database with:
– 4 ECPUs
– 1 TB of storage with storage auto-scaling and consuming 2 TB of storage

1-44