Oracle Cloud Infrastructure Documentation

Monitor Elastic Pool Usage and Cost Savings

Using an elastic pool provides up to 87% compute cost savings. You can get a detailed breakdown of elastic pool usage and the cost savings using the tools, views, and reports supported by Autonomous AI Database.

Topics:

Parent topic: Optimize Costs with Elastic Pools on Autonomous AI Database

OCI Usage Reports and OCI_USAGE_DATA View (for records until January 31, 2025)

You can use OCI usage reports and OCI_USAGE_DATA view to obtain elastic pool usage details in Oracle Cloud Infrastructure (OCI) until January 31, 2025.

See Cost and Usage Reports and OCI_USAGE_DATA_EXT View for more information.

Note

The OCI usage reports are deprecated. You can continue to access your existing usage report CSV files until July 31, 2025.

The following table shows the product/resource column values in an OCI usage report. The OCI usage report provides details on elastic pool usage for the pool leader and for pool members a given billing hour (similar information is available in OCI_USAGE_DATA view):

Elastic Pool Usage Type Billing Hour Values Shown
Member Compute Usage

For a given pool member where the product/resourceId column of the OCI usage report is equal to pool member’s OCID and the product/resource column of the OCI usage report is equal to PIC_ADBS_DB_ECPU_PEAK, the usage/billedQuantity of the OCI usage report shows the peak ECPU usage of the member in a specified billing hour.

You can use the following query to view the same usage details in the OCI_USAGE_DATA view: 

SELECT billed_quantity FROM OCI_USAGE_DATA
   WHERE resource_name='PIC_ADBS_DB_ECPU_PEAK' and
                resource_id=OCID_of_the_pool_member and
                interval_usage_start=start_time and
                interval_usage_end=end_time
Note

If a member has a local a local Autonomous Data Guard standby, its peak usage will be reported as two times (2 x) the peak usage. See About Billing Autonomous AI Database Elastic Pools with Autonomous Data Guard for more information.
Leader Compute Usage

For a given pool leader where the product/resourceId column of the OCI usage report is equal to pool leader's OCID and the product/resource column of the OCI usage report is equal to PIC_ADBS_DB_ECPU_PEAK, the usage/billedQuantity of the OCI usage report shows the peak ECPU usage of the leader in a specified billing hour.

You can use the following query to view the same usage details in the OCI_USAGE_DATA view: 

SELECT billed_quantity FROM OCI_USAGE_DATA
   WHERE resource_name='PIC_ADBS_DB_ECPU_PEAK' and
                resource_id=OCID_of_the_pool_leader and
                interval_usage_start=start_time and
                interval_usage_end=end_time
Note

If the leader has a local a local Autonomous Data Guard standby, its peak usage will be reported as two times (2 x) the peak usage. See About Billing Autonomous AI Database Elastic Pools with Autonomous Data Guard for more information.
Aggregated Pool Compute Usage

For a given pool leader where the product/resourceId column of the OCI usage report is equal to pool leader's OCID and the product/resource column of the OCI usage report is equal to PIC_ADBS_ELASTIC_POOL_DB_ECPU, the usage/billedQuantity of the OCI usage report shows the aggregated peak ECPU usage of the leader and all members in the specified billing hour.

You can use the following query to view the same usage details in the OCI_USAGE_DATA view: 

SELECT billed_quantity FROM OCI_USAGE_DATA
   WHERE resource_name='PIC_ADBS_ELASTIC_POOL_DB_ECPU' and
                resource_id=OCID_of_the_pool_leader and
                interval_usage_start=start_time and
                interval_usage_end=end_time

Notes for elastic pool billing information in the OCI usage report and the OCI_USAGE_DATA view:

  • Elastic pool aggregate peak ECPU usage is shown for terminated databases.

  • Elastic pool aggregate peak ECPU usage is shown for non-pool databases that were part of an elastic pool during a billing hour when the database was a member of an elastic pool.

See Billing Information: Autonomous AI Transaction Processing ECPU Compute Model and Track Oracle Cloud Infrastructure Resources, Cost and Usage Reports with Autonomous AI Database Views for more information.

OCI Cost Reports and OCI_COST_DATA View (for records after January 31, 2025)

You can use OCI cost reports and OCI_COST_DATA view to obtain elastic pool cost details in Oracle Cloud Infrastructure (OCI) after January 31, 2025.

See Cost and Usage Reports and OCI_COST_DATA_EXT View for more information.

The following table shows the product/resource column values in an OCI cost report. The OCI cost report provides details on elastic pool usage for the pool leader and for pool members for a given billing hour and similar information is available in OCI_COST_DATA view.

Elastic Pool Usage Type Billing Hour Values Shown
Member Compute Usage

For a given pool member where the product/resourceId column of the OCI cost report is equal to a pool member’s OCID and the product/Description column is equal to 'Autonomous Database - Elastic Pool Individual DB Peak ECPU', the usage/billedQuantity column of the OCI cost report shows the peak ECPU usage of the member in a specified billing hour.

You can use the following query to view the same usage details in the OCI_COST_DATA view: 

SELECT billed_quantity FROM OCI_COST_DATA
   WHERE product_description='Autonomous Database - Elastic Pool Individual DB  Peak ECPU' and
                resource_id=OCID_of_the_pool_member and
                interval_usage_start=start_time and
                interval_usage_end=end_time
Note

If a member has a local a local Autonomous Data Guard standby, its peak usage will be reported as two times (2 x) the peak usage. See About Billing Autonomous AI Database Elastic Pools with Autonomous Data Guard for more information.
Leader Compute Usage

For a given pool leader where the product/resourceId column of the OCI cost report is equal to pool leader's OCID, and the product/Description column is equal to 'Autonomous Database - Elastic Pool Individual DB Peak ECPU', the usage/billedQuantity column of the cost report shows the peak ECPU usage of the leader in a specified billing hour.

You can use the following query to view the same usage details in the OCI_COST_DATA view: 

SELECT billed_quantity FROM OCI_COST_DATA
    WHERE 
        product_description='Autonomous Database - Elastic  Pool Individual DB Peak ECPU' and
        resource_id=OCID_of_the_pool_leader and
        interval_usage_start=start_time and
        interval_usage_end=end_time
Note

If the leader has a local a local Autonomous Data Guard standby, its peak usage will be reported as two times (2 x) the peak usage. See About Billing Autonomous AI Database Elastic Pools with Autonomous Data Guard for more information.
Aggregated Pool Compute Usage

For a given pool leader where the product/resourceId column of the cost report is equal to pool leader's OCID and the product/Description column of the cost report is equal to product/Description column is equal to 'Autonomous Database - Elastic Pool ECPU', the usage/billedQuantity column of the cost report shows the aggregated peak ECPU usage of the leader and all members in the specified billing hour.

You can use the following query to view the same usage details in the OCI_COST_DATA view: 

SELECT billed_quantity FROM OCI_COST_DATA
   WHERE product_description='Autonomous Database - Elastic  Pool ECPU' and
            resource_id=OCID_of_the_pool_leader and
            interval_usage_start=start_time and
            interval_usage_end=end_time

Notes for elastic pool billing information in the OCI cost report and the OCI_COST_DATA view:

  • Elastic pool aggregate peak ECPU usage is shown for terminated databases.

  • Elastic pool aggregate peak ECPU usage is shown for non-pool databases that were part of an elastic pool during a billing hour when the database was a member of an elastic pool.

See Billing Information: Autonomous AI Transaction Processing ECPU Compute Model and Track Oracle Cloud Infrastructure Resources, Cost and Usage Reports with Autonomous AI Database Views for more information.

Elastic Pool Cost Savings Details in OCI

You can view the elastic pool cost savings achieved for your database from its Details page on the Oracle Cloud Infrastructure (OCI) console.

To view the elastic pool cost savings:

  1. On the Oracle Cloud Infrastructure console, click the hamburger menu in the top corner to display the navigation menu.
  2. Click Oracle AI Database in the navigation menu and select Autonomous AI Database.

    The Autonomous AI Databases page opens, showing the list of databases in your current Compartment.

  3. On the Autonomous AI Databases page, select your Autonomous Database from the links under the Display name column.
  4. On the Autonomous AI Database Information tab, under Resource Allocation, click the Actions icon next to Elastic pool, and select View elastic pool cost savings.

    The Elastic pool cost savings dialog opens.

    Note

    If the elastic pool is created in the current calendar month, the View Elastic Pool Cost Savings button remains disabled until the next calendar month.

  5. The Elastic pool cost savings dialog displays the following fields over the last three calendar months:
    • Usage with Elastic Pool:This field displays the cost of the elastic pool for the specific calendar month, measured in ECPU hours.
    • Estimated usage without Elastic Pool: This field displays the projected cost you would spend if you did not have an elastic pool.
    • Cost Savings with Elastic Pool: This field displays the cost savings in %. It is calculated based on the difference between Estimated usage without Elastic Pool and Usage with Elastic Pool.

  6. Optionally, you can toggle to enable the Display projected cost savings with auto scaling field. This toggle is disabled by default.

    When you enable the Display projected cost savings with auto scaling toggle, the Estimated usage without Elastic Pool field displays the projected cost you would spend if all your databases in the pool were out of the pool and used compute auto-scaling.

This clear presentation of cost savings provides transparent insight into the savings achieved through elastic pooling.