Provides information about elastic pool usage.

Notes for elastic pool usage:

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

• By default each instance in an elastic pool is automatically assigned a maintenance window. By selecting a pool shape that is 1024 ECPUs or greater, you have the option of assigning a custom 2-hour maintenance window during which the leader and all elastic pool members are patched together. To select a custom maintenance window for your elastic pool, file a Service Request at Oracle Cloud Support.

• Provisioning a pool leader or a member is subject to service limits enforced at the tenancy or compartment levels.

• In an elastic pool, the pool leader's licensing selections determine the license requirements for the entire pool. If you want to use BYOL for an elastic pool and set a BYOL License Limit, you must set the limit value on the pool leader's instance. The license selections for pool members, including any BYOL License Limit do not apply while an instance is a member of a pool. The license selections, including any BYOL License Limit, come into effect only if a pool member or the pool leader leaves the elastic pool.

  For example, if an elastic pool includes a member instance that uses Autonomous Data Guard with an 8 ECPU Primary with the BYOL license type set, the Primary and Standby instance's licensing selection is set as follows:

  • When the Primary is a pool member, the license type of the Primary can be set but it is does not apply for the Primary; the Primary uses the license type of the elastic pool leader. The license type selection on the Primary will apply when and if the Primary leaves the elastic pool.

  • For a local Standby, the Standby instance is in the elastic pool. In this case, the local Standby uses the same license type as the Primary.

  • For a cross-region Standby, the Standby instance is either in the pool (as a pool member or as the pool leader), or is not in the elastic pool, as follows:

    • When a cross-region Standby is not in the elastic pool, that is it is not either the pool leader or a pool member, then the cross-region Standby license type can be set but it is does not apply; the Standby uses the license type of the elastic pool leader. The license type selection on the Standby will apply when and if the Standby leaves the elastic pool.

    • When a cross-region Standby is not in the elastic pool, that is it is not either the pool leader or a pool member, then the cross-region Standby license type can be set but it is does not apply; the Standby uses the license type of the elastic pool leader. The license type selection on the Standby will apply when and if the Standby leaves the elastic pool.

    • When a cross-region Standby is not in the elastic pool, that is it is not either the pool leader or a pool member, then the cross-region Standby license type can be set but it is does not apply; the Standby uses the license type of the elastic pool leader. The license type selection on the Standby will apply when and if the Standby leaves the elastic pool.