Oracle Cloud Infrastructure Documentation

Remove Pool Members from an Elastic Pool

As an elastic pool member you can remove yourself from an elastic pool. As an elastic pool leader you can remove pool members from an elastic pool.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon 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.

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

  1. On the Details page, under Resource allocation, in the Elastic 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.

Parent topic: Use and Manage Elastic Pools on Autonomous Database

As Pool Leader Remove Members from an Elastic Pool

An elastic pool leader can remove pool members from an elastic pool.

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

    This shows the Elastic pool members area, with a list showing details for each instance that is an elastic pool member.

  2. Click more actions 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 an Elastic Pool

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

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

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

  • Billing for an Autonomous Database instance that leaves an elastic 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.