Adding Shards

Add shards to scale out your Globally Distributed Autonomous Database

You can add shards when:

You have completed Creating a Globally Distributed Autonomous Database Resource, but have not yet completed Deploying Globally Distributed Autonomous Database.
You have completed Deploying Globally Distributed Autonomous Database and want to scale up your Globally Distributed Autonomous Database with more shards.

On the Details page, on the Shards and Catalog tab, select Add Shard.
On the Add Shards pane configure the new shard.
In Shard Count indicate the number of shards you want to add, then configure them in the table below. You can add up to 10 shards in each set to deploy, and then add more after deployment if needed.
- Shard/Shardspace name - Shows the display name for each shard or shardspace in the configuration. Once you select a region the name is populated.
- Primary region - Select the primary region where you would like to host your shard
- Primary VM cluster - Select a cluster available in the selected primary region.
  
  Note:
  It is recommended that you use one VM cluster per database (shard or catalog).
- ECPU count - The number of ECPU cores to enable. Specify the number of ECPUs for your shard as an integer. Available cores are subject to your tenancy’s service limits.
- ECPU auto scaling - Enable automatic scaling based on workload per shard/shardspace
- Storage - GB of storage to allocate to your database
- Enable Data Guard - Instantiates Oracle Data Guard standby instances for each shard
- Data Guard region - Select the region where you would like to host the shard's Data Guard standby
- Data Guard VM Cluster - Select a cluster available in the selected Data Guard region.
  
  Note:
  You can select a cluster that contains a primary shard for a Data Guard standby database; however, it is recommended that you use one VM cluster per database (shard or catalog).
In Create administrator credentials, set the password for the shard database ADMIN user.
Select the Encryption key details for the new shards.
The encryption key settings you configure depend on the data distribution method configured for the Globally Distributed Autonomous Database when it was created.

Automated - All shards have the same encryption vault and encryption key, and is mandatory.

User managed - Each shard can have the same or different encryption key details, and is optional.

For both cases:
- Based on the primary region that you selected for the first shard, you select the vaults and encryption key available in that region and selected compartment.
- If Data Guard is enabled for a shard, and if the standby region is not the same as the primary region for that shard, you can select virtual private vaults that are replicated in the standby region.
Click Validate to run checks to make sure the new shards are valid.
Once any validation errors are addressed and validation is successful, click Add Shards to deploy the new shards.

Note:

There is a time limit for deploying new shards.

When scaling up a deployed Globally Distributed Autonomous Database, you must complete Deploying Globally Distributed Autonomous Database within 7 days of completing this procedure or you will get an error and must terminate the new shard resources and start again.
When adding shards to an undeployed Globally Distributed Autonomous Database, you have 7 days from completing Creating a Globally Distributed Autonomous Database Resource to add any shards and complete Deploying Globally Distributed Autonomous Database.

For more information about the concepts and considerations of adding shards to a Globally Distributed Autonomous Database see Shard Management in Using Oracle Sharding.

Parent topic: Create and Manage a Globally Distributed Autonomous Database