You create the resource in the Globally Distributed Autonomous AI Database home page.

1. Log in to the Console as a user with permissions to create Globally Distributed Autonomous AI Database resources, and navigate to the Globally Distributed Autonomous AI Database home page.

   See Interfaces to Globally Distributed Autonomous AI Database for details.

2. Click Create database.

3. In Provide basic information for the Globally Distributed Autonomous AI Database, provide the following information:

   Setting	Description and Notes
   Display name	Enter a user-friendly description or other information that helps you easily identify the distributed database. Avoid entering confidential information. You can modify this name after resource creation.
   Database name prefix	This prefix is appended to all of the database names in the configuration for ease of use.
   Compartment	Select a compartment to host the Globally Distributed Autonomous AI Database resource

4. In Tags you can add tags to the Globally Distributed Autonomous AI Database resource. These can also be added after creation.

5. In Configure database information, provide the following information:

   Setting	Description and Notes
   Deployment type	This setting is not configurable. Only Dedicated Infrastructure is supported.
   Workload type	This setting is not configurable. Only Transaction Processing is supported.
   Database version	You can select release 19c or 26ai

6. Configure Shards.

   Map and List View

   The Map view filters and shows you the available Exadata clusters where shards can be deployed.

   To add shards using the map, select an available region, then click Configure Shards, then configure the fields as described below.

   Use the Map toggle to select between the map and list view to configure the shards.

   Adding and Editing Shards

   Select Add Shard to add a shard to the list. This action may cause an Add Shard panel to open where you can enter details.

   You can select the Edit action item in the Actions list (…) to edit shard details.

   Configure the settings as described in the following table.

   Table 3-1 Shard Configuration Settings

   Setting	Description and Notes
   Data distribution	Automated Data is automatically distributed across shards using partitioning by consistent hash. The partitioning algorithm evenly and randomly distributes data across shards. User managed Lets you explicitly specify the mapping of data to individual shards. It is used when, because of performance, regulatory, or other reasons, certain data needs to be stored on a particular shard, and the administrator needs to have full control over moving data between shards. Note: For 26ai: Note that when Raft is selected in Replication type the User managed option is disabled. When you choose User managed data distribution, your Shards configuration settings apply to the shardspace rather than the shard itself.
   Shard count	When Map is enabled, this field cannot be edited. With Map disabled, you can enter the total number of shards to initially deploy in the distributed database. You can configure up to 10 shards in the initial deployment, and then add more later if needed.
   Replication type 26ai only	Raft replication creates replication units consisting of sets of chunks and distributes them automatically among the shards to handle chunk assignment, chunk movement, workload distribution, and balancing upon scaling. Note that when Raft replication is selected the User managed data distribution option is disabled. Data Guard is a shard-level replication solution which instantiates Oracle Data Guard standby databases for each shard. None is selected when you do not need replication. Note: Replication type can only be configured during this setup. You cannot change it later.
   Replication factor 26ai only	If Raft replication type is selected, you can set the Replication factor. Replication factor is the number of replicas in a replication unit. This number includes the leader replica and its followers.
   Shard/Shardspace name	The display name for each shard in the configuration. Selecting a region populates the field. Shardspace is displayed for User managed data distribution.
   Region	Select the OCI region where you would like to host your shard. Note that Automated data distribution with Data Guard replication type does not support shards in multiple regions.
   VM cluster	Select a cluster available in the selected region. Note: It is recommended that you use one VM cluster per database (shard or catalog).
   ECPU count	Enter the number of ECPU cores to enable for each shard. Specify the number of ECPUs as an integer. Available cores are subject to your tenancy’s service limits. You must enter a minimum of 2 ECPUs per shard. ECPUs are based on the number of cores, elastically allocated, from the shared pool of Exadata database servers and storage servers. Aggregated ECPU consumption on a given cluster is 1.5 times the ECPU count. Note that a number of ECPUs are consumed in overhead and are not available to the shards. See Oracle Cloud Infrastructure Documentation for more information.
   Auto scaling	Enable automatic scaling based on workload per shard/shardspace. This value is passed on to the Autonomous AI Database so that it can manage ECPU auto scaling. See Enable or Disable Auto Scaling of an Autonomous AI Database on Dedicated Exadata Infrastructure for details.
   Storage	GB of storage to allocate to the shard (database)

7. In Catalog configuration, provide the following information:

   You can choose to use the same configuration that is applied to the shards, or uncheck the Same as Shard's configuration box and make selections that apply only to the catalog database. The same fields are as described above for Shards.

   26ai: Note that Raft replication type does not apply to the catalog. You can uncheck Same as Shard's configuration and configure Data Guard if you want catalog replication.

8. In Create administrator credentials, create the user that will be able to access the shard catalog and all of the shards in the configuration.

9. In Encryption key, provide the following information:

   The encryption key settings you configure depend on the data distribution type you chose above.

   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 region that you selected for the first shard, you select the vaults and encryption key available in that region and selected compartment.
   • If you plan to configure Data Guard, and if the standby region is not the same as the primary region, you can select virtual private vaults that are replicated in the standby region.

10. Select character sets.

    Select the Character sets and National character sets that will be used in all of the shard and shard catalog databases. The AL32UTF8 character set is recommended by default for character sets and the AL16UTF16 character set is recommended by default for National character sets.

11. Select ports.

    Enter the Listener port, ONS port (local), and ONS port (remote).

    Note:

    The ONS port (remote) number must be unique to each Globally Distributed Autonomous AI Database. Do not reuse a port number used in another Globally Distributed Autonomous AI Database unless a delete operation is fully processed on the original.

    TLS port - TLS port number

    Note:

    The TLS port number must be unique to each Globally Distributed Autonomous AI Database. Do not reuse a port number used in another Globally Distributed Autonomous AI Database until a delete operation is fully processed on the original.

12. Advanced options: Shard configuration

    Chunks

    19c: Under Advanced Options you can optionally configure the number of chunks per shard. This setting is only applicable when Automated data distribution is selected.

    26ai: Under Advanced Options you can optionally configure the number of chunks per shard. This setting is only applicable when Automated data distribution is selected.

    Replication unit

    Available for release 26ai only

    If Raft replication type is selected, you can configure Replication unit.

    Under Advanced Options you can optionally configure the number of replication units created for the Globally Distributed Autonomous AI Database.

    When Raft replication is enabled, a Globally Distributed Autonomous AI Database contains multiple replication units. A replication unit is a set of chunks that have the same replication topology.

13. Advanced options: Backups configuration

    You can use the settings here to pass information to Autonomous AI Database to enable and configure automatic backups to Object Store.

    See Backup and Restore Autonomous AI Database on Dedicated Exadata Infrastructure for more details.

14. Select Validate to run validation checks against the configuration.

15. Once any validation errors are addressed and validation is successful, click Create.

    After you click Create, the Globally Distributed Autonomous AI Database display name appears in the list while the creation operation runs.

    The creation operation can take a while, because several tasks are performed as part of the create operation, including host procurement, installing software, and generating certificates for the shard directors (GSMs).

    You can monitor the operation status in the State column and track progress in the Work request tab. When the shard status is Available, Globally Distributed Autonomous AI Database creation is complete and successful.

    Caution:

    After a user creates a Globally Distributed Autonomous AI Database, do not move vaults and keys or the Globally Distributed Autonomous AI Database will not work.
16. When the Create process is complete you can continue to Managing Certificates, so you can download, sign, and upload the certificates for the GSMs.