Autonomous AI Database

To modify an existing Autonomous AI Database, follow these steps.

Manage an Autonomous AI Database
1. From the Oracle Database@Google Cloud dashboard , select Autonomous AI Database Service > Autonomous AI Database from the left-menu.
2. Select the Autonomous AI Database from the list.
3. Select the Manage in OCI link.
Switchover

Switchover is a planned transition from the primary database to standby database with no data loss. This operation is typically used for maintenance, testing, or proactively shifting the workloads.
These are the steps to perform a switchover of your Autonomous AI Database from the Oracle Database@Google Cloud dashboard.
1. Select Autonomous AI Database Service > Autonomous AI Database from the left-menu.
2. Select your Standby Autonomous AI Database.
3. Select the Switchover button.
  1. From the Select the region of the primary Autonomous AI Database drop-down list, select the region of the primary Autonomous AI Database.
  2. Enter your Autonomous AI Database ID in the confirmation field.
  3. Select the Confirm button to save your changes.
4. Navigate back to the Autonomous AI Databases list to check the Status of your Autonomous AI Database.
Failover

A failover is an unplanned operation that promotes the standby database to primary when the original primary becomes unavailable, which may result in data loss depending on the outage and data replication status. You should perform a switchover first and perform a failover when a switchover can not be completed such as in the event of a system failure or unplanned outage.
These are the steps to perform a failover of your Autonomous AI Database from the Oracle Database@Google Cloud dashboard.
1. Select Autonomous AI Database Service > Autonomous AI Database from the left-menu.
2. Select your Standby Autonomous AI Database.
3. Select the Failover button.
  1. From the Select the region of the primary Autonomous AI Database drop-down list, select the region of the primary Autonomous AI Database.
  2. Enter your Autonomous AI Database ID in the confirmation field.
  3. Select the Confirm button to save your changes.
    Note
    
    This operation is for disaster recovery only. It's irreversible, will cause some data loss, and will disconnect all clients. For planned events, always use a switchover to prevent data loss.
4. Navigate back to the Autonomous AI Databases list to check the Status of your Autonomous AI Database.
Disaster Recovery

This topic explains how to create a cross-region disaster recovery peer to protect your Autonomous AI Database instance from a complete region failure with a standby database or a backup copy in a different region than the primary database.
Complete the following steps to create a cross-region disaster recovery peer.
1. From the Google Cloud console, select Oracle Database@Google Cloud.
2. From the left-menu, select Autonomous AI Database Service and then Autonomous AI Database.
3. Select your Autonomous AI Database that you want to create disaster recovery peer.
4. Select the Disaster recovery tab, and then select the + Create button. Adding disaster recovery creates a peer database and incurs an additional cost.
5. From the Add peer database page, complete the following substeps:
  1. From the Region dropdown list, select region for Autonomous Data Guard.
    Note
    
    You can create up to 1 local peer and 1 cross-region peer for every remote paired region that your tenancy subscribed to
    
    If there is already a paired region, then that Region will not displayed in the list.
    
    Some regions have a paired region to support cross-region disaster recovery. The pairing is bi-directional and it will allow you to create a cross-region peer in a different region. You can only create a cross-region disaster recovery in a paired region. For more information, see the following table below.
    
    Table 1-1 Paired Regions
    
    Regional Pair A Regional Pair B
    
    US East US West
    
    UK South Germany Central
    
    US East US Midwest (Des Moines)
  2. From the Disaster recovery type section, select the checkbox to Enable cross-region backup replication to disaster recovery peer.
    Note
    
    For the disaster recover type, Autonomous Data Guard is a supported option.
    
    Cross-region Autonomous Data Guard standby databases incurs an additional cost.
    
    For Autonomous Data Guard, Recovery time objective is approximately 15 mins and Recovery point objective is approximately 1 min. For more information, see Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) .
  3. From the Network access for standby section, select your Network project, ODB Network and Client subnet.
    Note
    
    You can modify and manage your network settings within the OCI console after creating a peer database.
  4. Expand the Show Advanced settings section, enter an available IP address within the subnet's CIDR in the Private IP address field. Then, enter a name in the Hostname prefix field. The name can contain only letters and numbers, and a max of 63 characters.
  5. Review your information, and then select the Save button to create a peer database.
6. Once the process completes successfully, the Status changes to Available.
7. You can view the peer database in the resource list under the Disaster recovery tab.
1. To manage resource allocation, in the OCI console for the selected Autonomous AI Database, select the More actions button and the Manage resource allocation item from the menu. From the Manage resource allocation page, you can change the following options.
  1. In the Resources section, you can change the following.
    1. In the ECPU count field, you can enter a value.
    2. The Compute auto scaling checkbox enables or disables compute auto scaling as needed.
  2. In the Storage section, you can enter the following.
    1. In the Storage field, you can enter a value.
    2. In the Storage unit size drop-down, you can select GB or TB as needed.
    3. The Storage auto scaling checkbox enables or disables storage auto scaling as needed.
    4. The Allocated and Available fields are read-only calculated values.
    5. The Shrink button allows you to reduce the current Allocated storage of your database after you have deleted a significant amount of data. For more information, see Shrink Storage
    6. The Elastic pool checkbox enables or disables elastic storage if you have enabled it on your Autonomous AI Database. If it has not been enabled, this checkbox is unavailable.
    7. Select the Apply button to continue.
2. To configure the available tools, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Edit tool configuration item from the menu. From the Configure tools page, you can change the following options.
  1. All of the Autonomous AI Database tools have checkboxes allowing you to enable or disable the tool, including Graph studio, Oracle Machine Learning user interface, Data Transforms, and Data Lake Accelerator.
  2. Some of the Autonomous AI Database tools have an ECPU count field that allows you to control the number of ECPUs assigned to that tool, including Oracle APEX, Database actions, Graph studio, Oracle Machine Learning user interface, Data Transforms, Web Access (ORDS), MongoDB API, and Data Lake Accelerator.
  3. Some of the Autonomous AI Database tools with ECPU count fields also have an Maximum idle time (Minutes) field that allows you to control the time, in minutes, after which an idle process for that tool will be terminated.
  4. Select the Apply button to continue.
3. To change the adminstrator password, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Administrator password item from the menu. From the Administrator password page, you can change the following options.
  1. The Password and Confirm password fields are used to change the password, and the same complexity and reuse rules apply as during Autonomous AI Database creation.
  2. Select the Change button to continue.
4. To change the license type, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Update license and Oracle Database edition item from the menu. From the Update license and Oracle Database Edition page, you can change the following options.
  1. The Bring Your Own License (BYOL) checkbox can enabled or disabled.
  2. If Bring Your Own License (BYOL) is enabled, you can select the Oracle Database edition. See the ECPU limits for each addition in the help text.
  3. If Bring Your Own License (BYOL) is enabled, you can enable or disable the Enable BYOL ECPU limit checkbox. BYOL ECPU limits allow you to control how many ECPUs will be covered by BYOL licenses.Use the limit when the number of BYOL licenses you bring may not be enough to cover all of the database ECPUs you have provisioned, including auto-scale, disaster recovery peers, and database tools.
  4. If Bring Your Own License (BYOL) and Enable BYOL ECPU limit are enabled, enter a value in the Number of ECPUs to be covered by BYOL
  5. Select the Save button to continue.
5. To change the auto start/stop schedule, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Auto start/stop schedule item from the menu. From the Auto start/stop schedule page, you can change the following options.
  1. There are fields for the Start and Stop time for each day of the week in one (1) hour increments.
  2. Select the Apply button to continue.
6. To change encryption key, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Manage encryption key item from the menu. By default, your Autonomous AI Database uses Oracle-managed encryption keys during creation. From the Manage encryption key page, you can change the following options.
  1. Select either Encrypt using an Oracle-managed key or Encrypt using an customer-managed key.
  2. If you select Encrypt using an customer-managed key, you see the Key type drop-down of available customer-managed options. Select the one you want to use.
  3. Depending on the option you select, there may be additional fields and values required by that encryption key management option. For more information, see Use Customer-Managed Encryption Keys with Vault Located in Local Tenancy, Use Customer-Managed Encryption Key Located in a Remote Tenancy, AWS Key Management Service, or About Azure Key Vault as required.
  4. Select the Save button to continue.
7. To move a resource in your Autonomous AI Database, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Move resource item from the menu. From the Move resource page, you can change following.
  1. The Move resource page shows the current compartment at the top. In the Destination compartment enter a new compartment. You cannot move resources to the same compartment.
  2. Select the Move resource button when finished.
8. To add security attributes to your Autonomous AI Database, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Manage security attributes item from the menu. From the Manage security attributes page, you can change following.
  1. Select the Add security attribute button to add an attribute.
  2. The Namespace drop-down, the value should be selected if available. If not, for more information, see Zero Trust Packet Routing (ZPR)
  3. The Key and Value fields can be used needed.
  4. For more information on what you can do with tags, see Overview of Tagging.
  5. If you want to enter another tag, select the Add tag button.
  6. When you have added the tag(s) you want, select the Add button.
9. To add a tag to your Autonomous AI Database, in the OCI console for the selected Autonomous AI Database, select the Actions button and the Add Tags item from the menu. From the Add Tags page, you can change following.
  1. The Namespace drop-down is a single value None (free-form tag).
  2. The Key and Value fields can be used needed.
  3. For more information on what you can do with tags, see Overview of Tagging.
  4. If you want to enter another tag, select the Add tag button.
  5. When you have added the tag(s) you want, select the Add button.
There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.
There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

Regional Pair A	Regional Pair B
US East	US West
UK South	Germany Central
US East	US Midwest (Des Moines)

You can modify an Autonomous AI Database in Google Cloud using OCI Terraform provider.

Prerequisites

Terraform or OpenTofu installed
OCI credentials configured
HashiCorp OCI provider version >= 7.0
Autonomous AI Database is created using Terraform

To modify an Autonomous AI Database, perform the following steps:

Create a Modify configuration file and add the import block with the Autonomous AI Database id. The id value can be found at the Create Autonomous AI Database output block.

Sample Terraform Configuration using OCI Terraform Provider

# Set OCI Provider source and version
terraform {
  required_providers {
    # OCI Provider
    oci = {
      source = "oracle/oci"
      version = "7.29.0"
    }
  }
}

# Configure the OCI Provider
provider "oci" {
  tenancy_ocid = "ocid1.tenancy.oc1..aaaaaaaa2pg53mzroh6r2ub72r5mxxxxxxxxxxxxxpylciiqdihofe3dq" 
  user_ocid = "ocid1.user.oc1..aaaaaaaaa6wyl3kzbgogsqpsixxxxxxxxxxxxxxxxuwzkemcrgue5q" 
  private_key_path = "C:\\OCI-Terraform\\private-key.pem" # This example is for Windows OS
  fingerprint = "6c:c7:a7:60:f2:99:62:b9:8e:01:fc:e8:9b:eb:61:61"
  region = "us-desmoines-1" 
}

# Import OCI Autonomous Database Configuration
import {
    to = oci_database_autonomous_database.oci_adbs
    id = "ocid1.autonomousdatabase.oc1.us-desmoines-1.anrxkljrou6knaya7wgw7yyxxxxxxxxxxx7rj7dycpmayletmvxwmn32tywla"
}

Run the following commands in the Terminal window:

terraform init

terraform validate

terraform plan -generate-config-out="C:\GoogleCloud-Terraform\Working-Directory\generated_adbs.tf" # An example on Windows OS

Open the generated_adbs.tf file in a text editor and copy the content.
Append the generated_adbs.tf content in the Modify configuration file. Remove the import block.

Run the following command in the Terminal window:

terraform import oci_database_autonomous_database.oci_adbs "ocid1.autonomousdatabase.oc1.us-desmoines-1.anrxkljrou6knaya7wgw7yyxxxxxxxxxxx7rj7dycpmayletmvxwmn32tywla"  # Replace the OCID value

Run the following command in the Terminal window to confirm the imported state file and the generated configuration file resources are in sync:
```
terraform plan
```

Update the properties/values in the Modify configuration file as required.

Note

Modifying the configuration of Autonomous AI Database using OCI Terraform provider will make the Create configuration file out of sync. To avoid out of sync Force replacement / Destroy issue, add the following lifecycle block in the Create configuration file.

lifecycle {
    ignore_changes = [
      properties[0].compute_count,
      properties[0].data_storage_size_gb,
      properties[0].data_storage_size_tb,
      properties[0].db_version,
      properties[0].db_edition,
      properties[0].is_auto_scaling_enabled,
      properties[0].is_storage_auto_scaling_enabled,
      properties[0].backup_retention_period_days
    ]
  }

Sample Terraform Configuration using OCI Terraform Provider

# __generated__ by Terraform
# Please review these resources and move them into your main configuration files.

# __generated__ by Terraform from "ocid1.autonomousdatabase.oc1.us-desmoines-1.anrxkljrou6knaya7wgw7yyxxxxxxxxxxx7rj7dycpmayletmvxwmn32tywla"
resource "oci_database_autonomous_database" "oci_adbs" {
  autonomous_maintenance_schedule_type = "REGULAR"
  backup_retention_period_in_days      = 7
  character_set                        = "AL32UTF8"
  clone_table_space_list               = []
  compartment_id                       = "ocid1.compartment.oc1..aaaaaaaaqn5kip2ivclikxx5xxxxxxxiswrhoovfswhzc5rykq3wfkrdoa"
  compute_count                        = 2
  compute_model                        = "ECPU"
  cpu_core_count                       = 0
  data_safe_status                     = "NOT_REGISTERED"
  data_storage_size_in_gb              = 120
  database_edition                     = "STANDARD_EDITION"
  db_name                              = "demoadbstf"
  db_version                           = "23ai"
  db_workload                          = "OLTP"
  defined_tags = {
    "Oracle-Tags.CreatedBy" = "ocid1.multicloudlink.oc1.iad.amaaaaaaou6knayafyn3xxxxxxxxxeaolpk6i6lt6ygzgwiln3zdhyypbtq"
    "Oracle-Tags.CreatedOn" = "2026-01-17T02:59:48.527Z"
  }
  display_name                        = "demo-adbs-tf"
  enable_delete_scheduled_operations  = null
  freeform_tags                       = {}
  is_auto_scaling_enabled             = false
  is_auto_scaling_for_storage_enabled = false
  is_backup_retention_locked          = false
  is_data_guard_enabled               = false
  is_dedicated                        = false
  is_disconnect_peer                  = null
  is_free_tier                        = false
  is_local_data_guard_enabled         = false
  is_mtls_connection_required         = false
  key_version_id                      = null
  kms_key_id                          = "ORACLE_MANAGED_KEY"
  license_model                       = "BRING_YOUR_OWN_LICENSE"
  ncharacter_set                      = "AL16UTF16"
  nsg_ids                             = ["ocid1.networksecuritygroup.oc1.us-desmoines-1.aaaaaaaa5qxyfoeyhfc3he2deoxxxxxxxxxxxhs3uvn7lngjqsihxbsxq"]
  open_mode                           = "READ_WRITE"
  operations_insights_status          = "NOT_ENABLED"
  permission_level                    = "UNRESTRICTED"
  private_endpoint_ip                 = "192.168.4.194"
  private_endpoint_label              = "test"
  rotate_key_trigger                  = null
  security_attributes                 = {}
  standby_whitelisted_ips             = []
  state                               = "AVAILABLE" # "STOPPED"
  subnet_id                           = "ocid1.subnet.oc1.us-desmoines-1.aaaaaaaa2gn3z56wnz3ft2bxxxxxxxxxxxdjz7mminffoafmddq"
  switchover_to                       = null
  switchover_to_remote_peer_id        = null
  whitelisted_ips                     = []
  customer_contacts {
    email = "first.last@email.com"
  }
  db_tools_details {
    compute_count            = 0
    is_enabled               = false
    max_idle_time_in_minutes = 0
    name                     = "MONGODB_API"
  }
  db_tools_details {
    compute_count            = 0
    is_enabled               = true
    max_idle_time_in_minutes = 0
    name                     = "APEX"
  }
  db_tools_details {
    compute_count            = 0
    is_enabled               = true
    max_idle_time_in_minutes = 0
    name                     = "DATABASE_ACTIONS"
  }
  db_tools_details {
    compute_count            = 0
    is_enabled               = true
    max_idle_time_in_minutes = 0
    name                     = "ORDS"
  }
  db_tools_details {
    compute_count            = 32
    is_enabled               = true
    max_idle_time_in_minutes = 10
    name                     = "DLA"
  }
  db_tools_details {
    compute_count            = 8
    is_enabled               = true
    max_idle_time_in_minutes = 30
    name                     = "DATA_TRANSFORMS"
  }
  db_tools_details {
    compute_count            = 8
    is_enabled               = true
    max_idle_time_in_minutes = 60
    name                     = "GRAPH_STUDIO"
  }
  db_tools_details {
    compute_count            = 8
    is_enabled               = true
    max_idle_time_in_minutes = 60
    name                     = "OML"
  }
  encryption_key {
    autonomous_database_provider = "ORACLE_MANAGED"
  }
  resource_pool_summary {
    is_disabled = true
    pool_size   = 0
  }
  vanity_url_details {
    is_disabled = true
  }
}

Run the following command in the Terminal window:
```
terraform apply
```

Oracle Cloud Infrastructure Documentation

Autonomous AI Database