Use and Manage Elastic Resource Pools on Autonomous Database

Use an elastic resource pool to consolidate your Autonomous Database instances, in terms of their allocation of compute resources, and to provide up to 8 times cost savings.

Elastic resource pools help you improve operating efficiency and reduce costs by bringing all of your databases to the Cloud. This also supports consolidating resources and simplifying administration and operations by using Autonomous Database. When you need a large number of databases, that can scale up and down elastically without downtime, you can benefit by creating and using resource pools.

Elastic resource pools:

• Enable operating with a fixed budget for a group of databases, while delivering performance elasticity for each individual database.

• Allow for easy migration from on-prem Oracle environments that include oversubscription, to provide a cost effective way to move to Autonomous Database.

• Support SaaS vendors with a large number of individual customer databases.

• Provide resources for using a microservices architecture, where the ability to supply of large number of databases is required.

Note:

Elastic resource pools are only available for Autonomous Database instances that use the ECPU compute model and that are provisioned with the Transaction Processing or Data Warehouse workload types.

Topics

• About Elastic Resource Pools
  Use an elastic resource pool to consolidate your Autonomous Database instances, in terms of their allocation of compute resources, and to provide up to 8 times cost savings.
• Create Join or Manage a Resource Pool
  Shows the steps to create a resource pool, join a resource pool, or change the pool size for a resource pool.
• Create or Join a Resource Pool While Provisioning or Cloning an Instance
  You can create or join a resource pool when you provision or clone an Autonomous Database instance.
• List Resource Pool Members
  Shows the steps for the pool leader to list resource pool members.
• Remove Pool Members from a Resource Pool
  As a resource pool member you can remove yourself from a resource pool. As a resource pool leader you can remove pool members from a resource pool.
• Terminate a Resource Pool
  Shows the steps to terminate a resource pool. Only the pool leader can terminate a resource pool.
• Resource Pool Notes
  Provides information about resource pool usage.

About Elastic Resource Pools

Use an elastic resource pool to consolidate your Autonomous Database instances, in terms of their allocation of compute resources, and to provide up to 8 times cost savings.

When you create an elastic resource pool you select a pool size from a predefined set of pool sizes. Pool size determines how much you pay for compute as well as how many ECPUs you can provision in a given pool.

There are several terms to use when you work with elastic resource pools:

• Pool Leader: Is the Autonomous Database instance that creates a resource pool.

• Pool Member: Is an Autonomous Database instance that is added to a resource pool.

• Pool Size: Is a value that you set when you create a resource pool. The pool size must be one of the available resource pool shapes.

• Pool Shape: A pool shape is one of the valid pool sizes that you select when you create a resource pool. The pool shape must be one of: 128, 256, 512, 1024, 2048, or 4096 ECPUs.

• Pool Capacity: The pool capacity is the maximum number of ECPUs that a resource pool can use, and is four times (x4) the pool size.

Requirements to Create a Resource Pool

The following are the requirements for an Autonomous Database instance to create a resource pool and become a pool leader:

• The instance must use the ECPU compute model.

• The instance must be an Autonomous Database instance with the Transaction Processing workload type. This only applies for the pool leader. A resource pool can hold a mix of databases with Transaction Processing and Data Warehouse workloads.

• Auto scaling must be disabled.

• The instance must not be a member of an existing resource pool.

• The maximum allowed individual ECPU count for an Autonomous Database instance that creates a resource pool is 4 times the pool size specified when you create the pool.

• The instance that creates a resource pool is subject to tenancy limits. To create a resource pool you must have a sufficient number of ECPUs available, below the tenancy limit, to accommodate the size of the resource pool.

Requirements to Join a Resource Pool

The following are the requirements for an Autonomous Database instance to join a resource pool:

• The instance must use the ECPU compute model.

• A resource pool can contain Autonomous Database instances with either Transaction Processing or Data Warehouse workload types. A resource pool can hold a mix of databases with Transaction Processing and Data Warehouse workloads.

• Auto scaling must be disabled.

• The instance must not be a member of a resource pool.

• The maximum allowed individual ECPU count for an Autonomous Database instance is the available pool capacity. When an instance has an ECPU count greater than the available pool capacity, it is not allowed to join that resource pool.

Resource Leader and Member Instance ECPU Allocation

When an Autonomous Database instance is part of a resource pool, the minimum allowed individual ECPU allocation for an instance is 1 ECPU.

When an Autonomous Database instance is part of a resource pool, increments of 1 ECPU are allowed for individual Autonomous Database instance ECPU allocation.

Pool Capacity for a Resource Pool

A resource pool has a pool capacity of 4 times the pool size. For example, a pool with pool size of 128 ECPUs can hold up to 512 ECPUs for its leader and the members.

Note:

In these examples Autonomous Data Guard is not enabled. See About Elastic Resource Pools with Autonomous Data Guard Enabled for information on using resource pools with Autonomous Data Guard.

The following are examples of Autonomous Database instances that could be in a resource pool with a pool size of 128 and a pool capacity of 512 ECPUs:

• Each of these are valid for pool members in a resource pool with a pool size of 128 ECPUs:

  • 1 instance with 512 ECPUs, for a total of 512 ECPUs

  • 128 instances with 4 ECPUs, for a total of 512 ECPUs

  • 256 instances with 2 ECPUs, for a total of 512 ECPUs

• Similarly, each of the following are valid for pool members in a resource pool with a pool size of 128 ECPUs:

  • 1 instance with 128 ECPUs, 2 instances with 64 ECPUs, 32 instances with 4 ECPUs, and 64 instances with 2 ECPUs, for a total of 512 ECPUs

  • 256 instances with 1 ECPU, 64 instances with 2 ECPUs, for a total of 384 ECPUs, which is less than the pool capacity of 512 ECPUs.

Topics

• About Elastic Resource Pool Billing
  Elastic resource pool usage is billed to the pool leader and billing is based on the resource pool size and the actual hourly ECPU usage of the pool leader and the members. Resource pools have a pool capacity bigger than the pool size, where resource usage can exceed the pool size (up to 4x the pool size).
• About Elastic Resource Pools with Autonomous Data Guard Enabled
  The resource pool leader or members can enable either local or cross-region Autonomous Data Guard, or both local and cross-region Autonomous Data Guard.
• About Elastic Resource Pool Leader and Member Operations
  The Autonomous Database instance that creates a resource pool is the pool leader. Autonomous Database instances that are added to an existing pool are pool members. Depending on your role, either leader or member, you can perform operations on a resource pool.

About Elastic Resource Pool Billing

Elastic resource pool usage is billed to the pool leader and billing is based on the resource pool size and the actual hourly ECPU usage of the pool leader and the members. Resource pools have a pool capacity bigger than the pool size, where resource usage can exceed the pool size (up to 4x the pool size).

The billing for an elastic resource pool consists of only compute resources, that is ECPU usage, and all compute usage is charged to the Autonomous Database instance that is the pool leader. Individual Autonomous Database instances that are pool members are billed separately for storage usage. Any billing for storage is charged to individual Autonomous Database instances, independent of whether the instance is in a resource pool.

Using an elastic resource pool provides cost savings up to 8 times. For example, if you crate a resource pool with pool size of 128 ECPUs, you can provision up to the pool capacity size of 512 instances each with 1 ECPU, and pay for 128 ECPUs per billing hour (assuming usage per billing hour is at or below 128 ECPUs). Without elastic pools, you would have to create 512 individual Autonomous Database instances, each with a minimum of 2 ECPUs to accommodate 512 Autonomous Database instances. Billing in this example, without using a resource pool requires paying for 1024 ECPUs per billing hour, and billing for a resource pool of 128 ECPUs (up to 8 times cost savings).

After you create a resource pool, the total ECPU usage for a given hour is charged to the Autonomous Database instance that is the pool leader. With the exception of the pool leader, individual Autonomous Database instances that are pool members are not charged for ECPU usage while they are members of a resource pool.

Elastic resource pool billing is as follows:

• If the total ECPU utilization is equal to or below the pool size for a given hour, you are charged for the pool size number of ECPUs (1x the pool size).

  After a resource pool is created ECPU billing continues at a minimum of 1x the pool size rate, even when databases that are part of the pool are stopped. This applies to pool member databases and to the pool leader.

• If the aggregated peak ECPU utilization of the pool leader and the members exceeds the pool size at any point in time in a given billing hour:

  • Aggregated peak ECPU utilization of the pool is equal to or less than 2x of the pool size number of ECPUs: For usage that is greater than 1x the pool size number of ECPUs and up to and including 2x the number of ECPUs in a given billing hour: Hourly billing is 2x the pool size number of ECPUs.

  • Aggregated peak ECPU utilization of the pool is equal to or less than 4x the pool size number of ECPUs: For usage that is greater than 2x the pool size number of ECPUs and up and including to 4x the pool size number of ECPUs in a given billing hour: Hourly billing is 4x the pool size number of ECPUs.

  For example, consider a resource pool with a pool size of 128 ECPUs and a pool capacity of 512 ECPUs:

  • Case-1: The aggregated peak ECPU utilization of the pool leader and the members is 40 ECPUs between 2:00pm and 2:30pm, and 128 ECPUs between 2:30pm and 3:00pm.

    The resource pool is billed 128 ECPUs, 1x the pool size, for this billing hour (2-3pm). This case applies when the peak aggregated ECPU usage of the resource pool for the billing hour is less than or equal to 128 ECPUs.

  • Case-2: The aggregated peak ECPU utilization of the pool leader and the members is 40 ECPUs between 2:00pm and 2:30pm, and 250 ECPUs between 2:30pm and 3:00pm.

    The resource pool is billed 256 ECPUs, 2x the pool size, for this billing hour (2-3pm). This case applies when the peak aggregated ECPU usage of the resource pool for the billing hour is less than or equal to 256 ECPUs and greater than 128 ECPUs.

  • Case-3: The aggregated peak ECPU utilization of the pool leader and the members is 80 ECPUs between 2:00pm and 2:30pm, and 509 ECPUs between 2:30pm and 3:00pm.

    The resource pool is billed 512 ECPUs, 4x the pool size, for this billing hour (2-3pm). This case applies when the peak aggregated ECPU usage of the resource pool for the billing hour is less than or equal to 512 ECPUs and greater than 256 ECPUs.

Resource Pool Billing when a Resource Pool is Created or Terminated

When a resource pool is created or terminated, the leader is billed for the full hour for the resource pool. In addition, individual instances that are either added or removed from the pool are billed for any compute usage that occurs while the instance is not in the resource pool (in this case the billing applies to the individual Autonomous Database instance).

• Pool Creation Example: Assume there is an Autonomous Database instance with 4 ECPUs that is not part of any resource pool. At 2:15pm, if you create a resource pool with this instance with a pool size of 128 ECPUs, the instance becomes a pool leader. Assuming the Autonomous Database idles between 2-3pm, and there are no other Autonomous Database instances in the pool, billing for the hour between 2-3pm is as follows:

  The bill for the period 2-3pm is: (4 * 0.25) + 128 = 129 ECPUs

  Where the (4 * 0.25) is the billing for compute for the fifteen minutes before the Autonomous Database instance created the resource pool, and 128 ECPUs is the billing for the resource pool for the hour when the resource pool is created.

• Pool Termination Example: Assume an Autonomous Database instance with 4 ECPUs is the leader of a resource pool and the pool size is 128 ECPUs. At 4:30pm, if you terminate the resource pool, the database becomes a standalone Autonomous Database instance that is not part of any resource pool. Assuming the Autonomous Database idles between 4-5pm, and there are no other Autonomous Database instances in the pool, billing for the hour between 4-5pm is as follows:

  The bill for 4-5pm is: (4 * 0.5) + 128 = 130 ECPUs

  Where the (4 * 0.5) is the billing for compute for the thirty minutes after the Autonomous Database instance terminates the resource pool, and 128 ECPUs is the billing for the resource pool for the hour when the resource pool was terminated.

Resource Pool Billing with Built-in Tools

For either the pool leader or the members, compute resources that are allocated to the built-in tools, OML, Graph, or Data Transforms, are separate and do not count towards the resource pool total allocation. For billing purposes, the resource pool leader is billed for any built-in tool ECPU usage by either the leader or resource pool members, in addition to the resource pool ECPU usage.

For example, assume there is a resource pool with a pool size of 128 ECPUs; if in a given billing hour the aggregated peak ECPU utilization of the pool leader and the members is 80 ECPUs for the billing hour, and during this hour the combined total ECPU utilization for instances using built-in tools is 30 ECPUs, the leader is charged for the pool size (128 ECPUs), plus the built-in tool ECPU usage (30 ECPUs), for a total of 158 ECPUs for that hour.

About Elastic Resource Pools with Autonomous Data Guard Enabled

The resource pool leader or members can enable either local or cross-region Autonomous Data Guard, or both local and cross-region Autonomous Data Guard.

Local Autonomous Data Guard Standby Database Billing

Local peer database compute allocation is counted towards the resource pool capacity. When a pool leader or a pool member adds a local Autonomous Data Guard peer database, ECPU usage is 2x the pool member's individual ECPU allocation, and this ECPU usage counts towards the pool capacity.

For example, if you create a resource pool with a pool size of 128 ECPUs (with a pool capacity of 512 ECPUs), adding each of the following Autonomous Database instances of different sizes uses the entire resource pool capacity:

• 1 instance with 256 ECPUs with local Autonomous Data Guard enabled, for a total of 512 ECPUs allocation from the pool.

Similarly, if you create a resource pool with a pool size of 128 ECPUs (with a pool capacity of 512 ECPUs), adding the following Autonomous Database instances of different sizes uses the entire resource pool capacity:

• 128 instances with 2 ECPUs each with local Autonomous Data Guard enabled, for a total of 512 ECPUs allocation from the pool.

Cross-Region Autonomous Data Guard Standby Database Billing

Enabling Cross-region Autonomous Data Guard for a leader or for member has no effect on the resource pool capacity. A cross-region Autonomous Data Guard peer database has its own OCID and the cross-region peer is billed independently from the resource pool.

Note the following:

• Cross-region Autonomous Data Guard peer ECPUs do not use pool capacity and billing for Autonomous Data Guard cross-region peer databases happens on the peer instance.

• When the leader of a resource pool enables cross-region Autonomous Data Guard, the cross-region peer database ECPU allocation does not count towards the resource pool capacity. Billing for cross-region Autonomous Data Guard is on the cross-region instance, which is not part of the resource pool (resource pools do not operate across regions).

• When a member of a resource pool enables cross-region Autonomous Data Guard, the cross-region peer ECPU allocation does not count towards the pool capacity. Billing for cross-region Autonomous Data Guard is on the cross-region instance, which is not part of the resource pool (resource pools do not operate across regions).

For example, if you create a resource pool with a pool size of 128 ECPUs (with a pool capacity of 512 ECPUs), adding the following Autonomous Database instances of different sizes uses the entire resource pool capacity:

• A pool that contains the following instances:

  • 1 instance with 128 ECPUs with cross-region Autonomous Data Guard enabled (using a total of 128 ECPUs from the pool).

  • 64 instances with 2 ECPUs each with both local and cross-region Autonomous Data Guard enabled (using a total of 256 ECPUs from the pool).

  • 128 instances with 1 ECPU, each with cross-region Autonomous Data Guard enabled (using 128 ECPUs from the pool).

About Elastic Resource Pool Leader and Member Operations

The Autonomous Database instance that creates a resource pool is the pool leader. Autonomous Database instances that are added to an existing pool are pool members. Depending on your role, either leader or member, you can perform operations on a resource pool.

Pool Leader Operations

The following operations are valid only for the pool leader:

Operation	Description
Create a resource pool	The Autonomous Database instance that creates a resource pool is the pool leader. See Create Join or Manage a Resource Pool for more information.
Remove a resource pool member	A resource pool leader can remove a member from the resource pool. See As Pool Leader Remove Members from a Resource Pool for more information.
Terminate a resource pool	When a resource pool has no pool members, the pool leader can terminate the resource pool. See Terminate a Resource Pool for more information.
Modify resource pool size	A resource pool leader can modify the pool size. See Change the Resource Pool Shape for more information.
List pool members	A pool leader can list pool members. See List Resource Pool Members for more information.

Pool Member Operations

The following operations are valid for a pool member or for the pool leader:

Operation	Description
Add instance to resource pool	An Autonomous Database instance can be added as a pool member as long as the instance has either Transaction Processing or Data Warehouse workload type, the instance uses the ECPU compute model, and the instance is not a pool member of a different pool. See Join an Existing Resource Pool for more information.
Remove a resource pool member	A resource pool member can remove themselves from the resource pool. See Remove Pool Members from a Resource Pool for more information.

Create Join or Manage a Resource Pool

Shows the steps to create a resource pool, join a resource pool, or change the pool size for a resource pool.

• 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 click Autonomous Transaction Processing.

• On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.

To create a resource pool:

Note:

To create a resource pool the instance must use the ECPU compute model and the workload type must be Transaction Processing.

1. On the Autonomous Database Details page select Manage resource allocation.

   Verify that Compute auto scaling is disabled.

   If Compute auto scaling is selected, disable Compute auto scaling:

   1. In the Manage resource allocation area, deselect Compute auto scaling.
   2. Click Apply.

      The Lifecycle state changes to Scaling in Progress. After some time the Lifecycle state changes to Available.

   3. On the Autonomous Database Details page select Manage resource allocation to display the Manage resource allocation area.
2. In the Manage resource allocation area, click Show advanced options.
3. Select Enable resource pool.
4. Select Create a resource pool.
5. Enter or choose a pool size in the Pool ECPU count field.

   Select a pool size from the list of pool shapes: 128, 256, 512, 1024, 2048, or 4096.

6. Click Apply to create the resource pool.

When you click Apply, the Lifecycle state changes to Scaling in Progress. After the Lifecycle state changes to Available the changes apply immediately.

After you create a resource pool, click Manage resource allocation to display the resource pool information. In the Manage resource allocation area, the Resource pool field shows Enabled, the Pool role field shows Leader, and the Pool ECPU count field shows the pool size you selected.

Description of the illustration adb_resource_pool_leader.png

• Join an Existing Resource Pool
  Shows the steps to join an existing resource pool.
• Change the Resource Pool Shape
  Shows the steps for the pool leader to change the resource pool shape for an existing resource pool.

Join an Existing Resource Pool

Shows the steps to join an existing resource pool.

To join a resource pool, the following is required for the Autonomous Database instance:

• The instance must use the ECPU compute model.

  See Compute Models in Autonomous Database for more information.

• The workload type must be one of Transaction Processing or Data Warehouse.

  See About Autonomous Database Workload Types for more information.

• Auto scaling must be disabled.

• The instance must not be a member of a resource pool.

To join a resource pool:

1. On the Autonomous Database Details page select Manage resource allocation.

   Verify that Compute auto scaling is disabled.

   If Compute auto scaling is selected, disable Compute auto scaling:

   1. In the Manage resource allocation area, deselect Compute auto scaling.
   2. Click Apply.

      The Lifecycle state changes to Scaling in Progress. After some time the Lifecycle state changes to Available.

   3. On the Autonomous Database Details page select Manage resource allocation to display the Manage resource allocation area.
2. In the Manage resource allocation area, click Show advanced options to show the advanced options.
3. Select Enable resource pool.
4. Select Join an existing resource pool.
5. In the Select pool leader in compartment field choose a pool leader in a compartment.
   1. Use the compartment shown or click Change Compartment to select a different compartment.
   2. Select a pool leader from the list of available pool leaders in the selected compartment.
6. Click Apply to add the instance to the resource pool.

When you click Apply the Lifecycle state changes to Scaling in Progress. After the Lifecycle state changes to Available the changes apply immediately.

After you create a resource pool, click Manage resource allocation to see the resource pool details. In the Manage resource allocations area, under Resource pool, the Resource pool field shows Enabled, the Pool role field shows Member, and the Resource pool leader field shows a link to the pool leader.

Change the Resource Pool Shape

Shows the steps for the pool leader to change the resource pool shape for an existing resource pool.

Note:

Only a pool leader can modify the pool shape.

To change the shape of a resource pool (update the pool size):

1. On the Autonomous Database Details page select Manage resource allocation to display the Manage resource allocation area.
2. In the Pool ECPU count field, select a value that is different than the current value
3. Click Apply.

   When you click Apply, the Lifecycle state changes to Scaling in Progress. After the Lifecycle state changes to Available the changes apply immediately.

Note:

Decreasing the CPU allocation, Pool ECPU count, to a value that cannot accommodate all the members of the resource pool is not allowed.

For example, for a resource pool with a Pool ECPU count of 256 ECPUs and a pool capacity of 1024 ECPUs: If the resource pool contains eight (8) Autonomous Database instances with 80 ECPUs each for a total of 640 ECPUs, the resource pool leader cannot decrease the Pool ECPU count to 128 ECPUs. In this case, if the pool size were reduced to 128 ECPUs, the pool capacity would be 512 ECPUs, which is less than the total allocation for the pool members (640 ECPUs).

Create or Join a Resource Pool While Provisioning or Cloning an Instance

You can create or join a resource pool when you provision or clone an Autonomous Database instance.

See Provision Autonomous Database for details on how to create an Autonomous Database for your workload type using the Create Autonomous Database dialog.

See Clone an Autonomous Database Instance or Clone an Autonomous Database from a Backup for details on cloning.

To create a resource pool while provisioning or cloning:

Note:

To create a resource pool the instance must use the ECPU compute model and the workload type you select must be Transaction Processing.

1. In the Configure the database area, click Show advanced options to show advanced options.
2. Deselect Compute auto scaling.
3. Select Enable resource pool.
4. Select Create a resource pool.
5. In the Pool ECPU count field, select a pool size from the list of pool shapes.

   The valid values that you can select are: 128, 256, 512, 1024, 2048, or 4096.

   
   Description of the illustration adb_resource_pool_create.png
6. Complete the remaining provisioning or cloning steps, as specified in Provision Autonomous Database, Clone an Autonomous Database Instance, or Clone an Autonomous Database from a Backup.

To join an existing resource pool while provisioning or cloning:

Note:

To join a resource pool the instance must use the ECPU compute model and the workload type must be one of Transaction Processing or Data Warehouse.

1. In the Configure the database area, click Show advanced options to show advanced options.

2. Deselect Compute auto scaling.

3. Select Enable resource pool.

4. Select Join an existing resource pool.

5. In the Select pool leader in compartment field choose a pool leader in a compartment.

   1. Use the compartment shown or click Change Compartment to select a different compartment.

   2. Select a pool leader from the list of available pool leaders in the selected compartment.

   
   Description of the illustration adb_resource_pool_join.png

6. Complete the remaining provisioning or cloning steps, as specified in Provision Autonomous Database, Clone an Autonomous Database Instance, or Clone an Autonomous Database from a Backup.

List Resource Pool Members

Shows the steps for the pool leader to list resource pool members.

To list resource pool members:

1. On the resource pool leader's Autonomous Database details page, under Resources, click Resource pool members.
2. The Resource pool members area shows a list of resource pool members.

This shows the list of resource pool members for the leader Autonomous Database instance.

If you click at the end of a row in the list, you can select an action to perform for the member. The possible actions are:

• View details: Shows the member's Oracle Cloud Infrastructure Console

• Copy OCID: Copies the member's Autonomous Database instance OCID.

• Remove from pool: Brings up a dialog where you can confirm to remove the Autonomous Database instance from the pool.

Remove Pool Members from a Resource Pool

As a resource pool member you can remove yourself from a resource pool. As a resource pool leader you can remove pool members from a resource pool.

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 or Autonomous Transaction Processing.

• On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.

As a pool member, you can remove your instance from a resource pool:

1. On the Details page, under Resource allocation, in the Resource pool field click Leave pool.

   This shows the Leave pool confirmation dialog.

2. In the Leave pool confirmation dialog, enter the database name.
3. Click Leave.

   When you click Leave, the Lifecycle state changes to Scaling in Progress. After the Lifecycle state changes to Available the changes apply immediately.

• As Pool Leader Remove Members from a Resource Pool
  A resource pool leader can remove pool members from a resource pool.
• Notes for Leaving a Resource Pool
  Provides information about resources when a member or the leader leaves a resource pool.

As Pool Leader Remove Members from a Resource Pool

A resource pool leader can remove pool members from a resource pool.

1. On the Autonomous Database Details page, under Resources, click Resource pool members.

   This shows the Resource pool members area, with a list showing details for each instance that is resource pool member.

2. Click at the end of a row for an instance you want to remove and in the drop down list select Remove from pool.

   This shows the Remove from pool confirmation dialog.

3. Click Leave to confirm.

   When you click Leave, the Lifecycle state changes to Scaling in Progress. After the Lifecycle state changes to Available the changes apply immediately.

Notes for Leaving a Resource Pool

Provides information about resources when a member or the leader leaves a resource pool.

• When a pool member or the leader leaves a resource pool, auto scaling is disabled. After leaving the resource pool you can enable auto-scaling for the instance.

• When a pool member leaves a resource pool, the resource pool has more resources available. For example, if the resource pool were fully allocated up to the pool capacity, and an instance with 10 ECPUs leaves the pool, the resource pool would have 10 available ECPUs.

• Billing for an Autonomous Database instance that leaves a resource pool returns to individual instance billing, based on the compute and storage resources that the individual instance uses:

  • If a pool member with 2 ECPUs or more leaves the pool, the individual instance's ECPU allocation remains and the instance is billed for that number of ECPUs.

  • If a pool member with 1 ECPU leaves the pool, the ECPU allocation is automatically set to 2 ECPUs and the instance is billed for 2 ECPUs going forward, unless it's scaled up.

Terminate a Resource Pool

Shows the steps to terminate a resource pool. Only the pool leader can terminate a resource pool.

Note:

Terminating a resource pool is only allowed when there are no pool members in the resource pool.

• 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 or Autonomous Transaction Processing.

• On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.

To terminate a resource pool:

1. On the Autonomous Database Details page, select Manage resource allocation.
2. Select Terminate pool.
3. Click Apply to terminate the resource pool.

When you click Apply, the Lifecycle State changes to Scaling in Progress. After the Lifecycle State changes to Available the changes apply immediately.

Resource Pool Notes

Provides information about resource pool usage.

Starting and stopping Autonomous Database instances that are members of a resource pool does not depend on the state of the leader. That is, you can independently stop and start each instance that is part of a resource pool, including the leader and members of the resource pool that are not the leader.