What’s New in ADB-D on Exadata Cloud@Customer

Here’s a summary of the noteworthy ADB-D on Exadata Cloud@Customer additions and enhancements.

Configure Non-Default SCAN Listener Ports

  • Services: Database
  • Release Date: November 15, 2022
This feature enables you to:
  • Choose a Single Client Access Name (SCAN) listener port for Transport Layer Security (TLS) and non-TLS from a range of available ports. For TLS, the default is 2484; for non-TLS, it is 1521.
  • Choose between one-way TLS and mutual TLS (mTLS) for database client connections. ORDS is always one-way TLS as it currently is.

Clone an Autonomous Database Across Exadata Infrastructure Within the Same Region

  • Services: Database
  • Release Date: August 09, 2022

With this enhancement, you can clone an ADB from an ACD in one Exadata Infrastructure to an ACD in another Exadata Infrastructure within the same region.

Character Set Selection

  • Services: Database
  • Release Date: May 17, 2022

This feature enhancement enables you to specify the database character set and the national character set while creating an ADB.

  • While creating an ADB, you can choose only the character sets supported. To get the complete list of supported character sets, use ListAutonomousDatabaseCharacterSets API.
  • You cannot change the character set after creating an ADB.
  • You can only set the character sets while creating an ADB. Character set selection is not supported for cloning (meta or full) or creating from a backup.
  • The CDB will remain using AL32UTF8 for the database character set and AL16UTF16 for the national character set.
  • Each ADB in an ACD can have different combinations of database/national character sets.

Enhanced Resource Tracking for Autonomous Database

  • Services: Database
  • Release Date: May 10, 2022

Identify where the reclaimable OCPUs are located to reclaim them to create new database resources or for scaling automation when a certain threshold is reached.

You can create multiple AVMCs on an Exadata Infrastructure resource. The OCPUs that you allocate while provisioning the AVMC resource will be the Total OCPUs available for its Autonomous Databases. When you create multiple AVMCs, each AVMC can have its own value for total OCPUs.

At an AVMC or ACD level, the total number of OCPUs available for creating databases is called Available OCPUs.

This feature enhancement provides better resource usage tracking:
  • Reclaimable OCPUs:

    When an Autonomous Database is terminated or scaled down, the number of OCPUs allocated to it is not immediately returned to the available OCPUs at its parent AVMC level for the overall deployment. They continue to be included in the count of OCPUs available to its parent container database until that parent container database is restarted. These OCPUs are called reclaimable OCPUs. Reclaimable OCPUs at the parent AVMC level are the sum of reclaimable OCPUs of all its ACDs. When an ACD is restarted, it returns all its reclaimable OCPUs to the available OCPUs at its parent AVMC level.

  • Failure free ADB Provisioning with Provisionable OCPUs:

    Based on the resource utilization on each node; not all the values of the available OCPUs can be used to provision or scale Autonomous Databases. For example, suppose you have 20 OCPUs available at the AVMC level, not all the values from 1 to 20 OCPUs can be used to provision or scale Autonomous Databases depending on the resource availability at the node level. The list of OCPU values that can be used to provision or scale an Autonomous Database is called Provisionable OCPUs.

    On the console, when you try to provision or scale an Autonomous Database, the OCPU count will be validated against the list of provisionable OCPUs, and if the value is not provisionable, you will be provided with the two nearest provisionable OCPU values. Alternatively, if you want to see the complete list of provisionable OCPU values for an Autonomous Exadata VM Cluster, you can use the following API:

    GetAutonomousContainerDatabase returns a list of provisionable OCPU values that can be used to create a new Autonomous Database in the given Autonomous Container Database. See GetAutonomousContainerDatabase for more details.

    GetAutonomousDatabase returns a list of provisionable OCPU values that can be used for scaling a given Autonomous Database. See GetAutonomousDatabase for more details.

Autonomous VM Clusters

As a Fleet Administrator, you will be able to identify:

  • Total OCPUs: The number of CPU cores allocated to the VM Cluster.
  • Exadata Storage (TB): The storage allocated to the VM Cluster in TBs.
  • Total Autonomous Database Storage (TB): Total Autonomous Database Storage storage allocated to the Autonomous VM Cluster.
  • Available Autonomous Database Storage (TB): Storage available to create Autonomous Databases in the Autonomous VM Cluster
  • Total Memory: The memory allocated to the VM Cluster in GB.
  • Total Local Storage (GB): Total Local Storage in the Exadata Infrastructure.
  • Available OCPUs: CPU cores available for allocation to ADBs.
  • Reclaimable OCPUs: Sum of all the reclaimable OCPUs in all the ACDs in the Autonomous VM Cluster.
  • Available ACDs: The number of ACDs you can create in the AVM using the available resources.
  • Total ACDs: Number of ACDs customers want to create in the AVM.
  • Which ACDs have a lot of reclaimable OCPUs and restart them when needed.

Autonomous Container Database

As a Database Administrator, you will be able to identify:

  • Total OCPUs: The number of CPU cores allocated to the VM cluster.
  • Available OCPUs: Sum of OCPU available on the Autonomous VM Cluster + Reclaimable OCPU within the same ACD.
  • Reclaimable OCPUs: When an Autonomous Database is terminated or scaled down, the number of OCPUs allocated to it is not immediately returned to the available OCPUs at its parent AVMC level for the overall deployment. They continue to be included in the count of OCPUs available to its parent container database until that parent container database is restarted. These OCPUs are called reclaimable OCPUs. Reclaimable OCPUs at the parent AVMC level are the sum of reclaimable OCPUs of all its ACDs. When an ACD is restarted, it returns all its reclaimable OCPUs to the available OCPUs at its parent AVMC level.
Note

You cannot create an ACD if 2 OCPUs are not available in the VM Cluster or Exadata Infrastructure.

Autonomous Database

As a Database Administrator, you will be able to identify the OCPU count that you can use to provision or scale an ADB.

  • OCPU: The number of OCPU cores to be made available to the database.
  • Storage: The quantity of storage available to store data in the database, in terabytes.
  • While provisioning an ADB, if you specify an OCPU count that the service cannot provision in the existing ACD, then the service displays an error message and suggests 2 values in close proximity to the value that you have specified.

    For example, assume that you are creating an ADB with 15 OCPUs on a Quarter Rack Exadata Infrastructure that has 20 OCPUs available. However, there are only 10 OCPUs available on each node. In this case, the service will not be able to provision the ADB because 15 OCPUs is less than the split threshold of 16 OCPUs. Therefore, the nearest possible values are 17 and 18.

  • While scaling an ADB, if you specify an OCPU count that the service cannot use to scale the ADB, then the service displays an error message and suggests 2 values in close proximity to the value that you have specified.

Table 6-1 REST API Endpoints to Track and Manage Resource Usage

REST API Endpoint Description

GetAutonomousVmCluster

View a list of available OCPU, reclaimable OCPU, available Autonomous Database storage, and available ACDs.

GetAutonomousContainerDatabase

  • View a list of available OCPU, total OCPU, and reclaimable OCPU.
  • View an array of provisionable OCPUs.

GetAutonomousDatabase

View an array of scalable OCPUs.

Longer Database Name

  • Services: Database
  • Release Date: May 03, 2022

The length of the database name has been extended from 14 characters to 30 characters. Specify a user-friendly name that you can use to identify the database. The database name must contain only the permitted characters.

Review the following guidelines when selecting a database name:

  • maximum of 30 characters
  • contain only alphanumeric characters
  • begin with an alphabetic character
  • must not contain spaces

Create a New Autonomous Database Instance from Backup

  • Services: Database
  • Release Date: April 12, 2022

Restore an Autonomous Database (ADB) backup to an Autonomous Container Database (ACD) on the same or a different Autonomous Virtual Machine (AVM) running on the existing or different Autonomous Exadata Cloud@Customer system.

Prerequisites and Limitations

  • If you are using customer-managed keys, then the target AVM/ACD will require access to the source Oracle Key Vault (OKV) for the keys.
  • The target AVM must have access to the backup destination of the source for the restore to be possible.
  • You can only use the Full Clone option to create a database clone.
  • You cannot use disk-based backups to create ADB instances from backups.
  • Target ACD must be on the same or higher version as the source.
  • One ADB restore per AVM. The limit applies only to the target AVM.

Multiple Autonomous VM Cluster Support

  • Services: Database
  • Release Date: March 15, 2022

Multi-VM Cluster supports heterogeneous computing environments in which Autonomous and Non-Autonomous VM clusters can coexist on an Exadata Infrastructure.

With Multiple VM Cluster support you can:
  • Create multiple Autonomous VM Clusters on an Exadata Infrastructure
  • Schedule separate maintenance runs for each Autonomous VM Cluster
  • Use different license models for each Autonomous Database

Automatic Failover with a Standby Autonomous Container Database

  • Services: Database
  • Release Date: January 18, 2022

With Fast-Start Failover (FSFO), the system automatically detects the failure of the primary Autonomous Container Database and then fails over to a designated standby Autonomous Container Database.

Automatic failover is optional while configuring Autonomous Data Guard. You can enable or disable automatic failover after configuring Autonomous Data Guard.

X9M-2 System Support

  • Services: Database
  • Release Date: September 28, 2021

Oracle Exadata Cloud@Customer comes in different infrastructure shapes to support workloads of different sizes. In this release, the capability of Oracle Exadata Cloud@Customer has been extended to support X9M-2 system.

For more information, see Available Exadata Infrastructure Hardware Shapes.

Fractional OCPU and GB Storage

  • Services: Database
  • Release Date: June 15, 2021

Create Autonomous Databases with less than 1 OCPU count using fractional units from 0.1 to 0.9 OCPU and GB sizing between 32 GB and the maximum usable storage for your Exadata shape.

Autonomous Data Guard Enabled Autonomous Database and Oracle Key Vault (OKV) Integration

  • Services: Database
  • Release Date: June 15, 2021

Integrate your on-premises Oracle Key Vault (OKV) with Autonomous Data Guard enabled Autonomous Databases on Exadata Cloud@Customer and use customer-managed keys stored in Oracle Key Vault to secure your critical data.

Infrastructure Patching

  • Services: Database
  • Release Date: May 04, 2021

ADB-Dedicated maintenance involves patching Exadata Infrastructure(EI) Autonomous VM Cluster, and Autonomous Container Database (ACD).

Access Control List (ACL) to Restrict Access to Autonomous Data Guard Enabled Autonomous Databases

  • Services: Database
  • Release Date: January 26, 2021

An access control list (ACL) provides additional protection to your database by allowing only the clients with specific IP addresses to connect to the database. You can add IP addresses individually, or in CIDR blocks.

ADB-D on Exadata Cloud@Customer: Monitor Performance with Autonomous Database Metrics

  • Services: Database
  • Release Date: December 15, 2020

You can monitor the health, capacity, and performance of your Autonomous Databases with metrics, alarms, and notifications. You can use Oracle Cloud Infrastructure console or Monitoring APIs to view metrics.

ADB-D on Exadata Cloud@Customer: Autonomous Data Guard

  • Services: Database
  • Release Date: November 17, 2020

Enabling Autonomous Data Guard on an Autonomous Container Database on dedicated Exadata infrastructure creates a standby (peer) Autonomous Container Database that provides data protection, high availability, and facilitates disaster recovery for the primary database.

Access Control List (ACL) to Restrict Access to Autonomous Databases

  • Services: Database
  • Release Date: November 10, 2020

An access control list (ACL) provides additional protection to your database by allowing only the clients with specific IP addresses to connect to the database. You can add IP addresses individually, or in CIDR blocks.

Oracle Key Vault (OKV) Integration

  • Services: Database
  • Release Date: October 27, 2020

Integrate your on-premises Oracle Key Vault (OKV) with Autonomous Database on Exadata Cloud@Customer to secure your critical data on-premises.

Oracle Key Vault integration enables you to take complete control of your encryption keys and store them securely on an external, centralized key management device.

X8M-2 System Support

Per-Second Billing for Autonomous Database OCPU Usage

Oracle Autonomous Database on Oracle Exadata Database Service on Cloud@Customer