Oracle Cloud Infrastructure Documentation

What’s New in Oracle Exadata Database Service on Exascale Infrastructure

Oracle is constantly adding new capabilities to Oracle Exadata Database Service on Exascale Infrastructure.

New Regions and Realms for ExaDB-XS

Oracle continues to add new regions for Oracle Exadata Database Service on Exascale Infrastructure (ExaDB-XS).

Note

Where the region supports multiple availability domains (AD), only a single availability domain is supported with Oracle Exadata Database Service on Exascale Infrastructure.

Release Date: January 22, 2025

ExaDB-XS is now available in the following regions:

  • PHX: US West (Phoenix)
  • VCP: Brazil Southeast (Vinhedo)

Release Date: January 14, 2025

YUL: Canada Southeast (Montreal)

Release Date: December 19, 2024

MRS: France South (Marseille)

Release Date: December 12, 2024

ExaDB-XS is now available in the following regions:

  • AUH: UAE Central (Abu Dhabi)
  • KIX: Japan Central (Osaka)
  • YNY: South Korea North (Chuncheon)

Release Date: November 5, 2024

ExaDB-XS is now available in the following regions:

  • LHR: UK South (London)
  • ZRH: Switzerland North (Zurich)
  • BOG: Colombia Central (Bogota)

Release Date: November 1, 2024

ExaDB-XS is now available in the following regions:

  • NRT: Japan East (Tokyo)
  • ICN: South Korea Central (Seoul)
  • YYZ: Canada Southeast (Toronto)

Release Date: October 24, 2024

ExaDB-XS is now available in the following regions:

  • CDG: France Central (Paris)
  • GRU: Brazil East (Sao Paulo)
  • JED: Saudi Arabia West (Jeddah)
  • MEL: Australia Southeast (Melbourne)
  • SIN: Singapore (Singapore)
  • SYD: Australia East (Sydney)

Release Date: October 1, 2024

ExaDB-XS is now available in the following regions:

  • BOM: India West (Mumbai)
  • HYD: India South (Hyderabad)

Release Date: September 2024

The initial release of ExaDB-XS is available in four regions:

  • SJC: US West (San Jose)
  • IAD: US East (Ashburn)
  • FRA: Germany Central (Frankfurt)
  • JNB: South Africa Central (Johannesburg)

Scale ECPUs to Zero

You can now scale ECPUs enabled per VM to zero on ExaDB-XS.

Release Date: January 14

We are pleased to announce general availabilility of a new feature that allows users to scale the Enabled ECPUs of an ExaDB-XS VM Cluster to zero. This ability enables you to temporarily shut down the VM cluster and avoid billing related to usage of Enabled ECPUs while in this shutdown state.

Deploy Single Node VM Clusters

You can deploy and run databases in a single-node cluster without requiring an Oracle Real Application Clusters (Oracle RAC) license.

Release Date: January 22

We are pleased to announce the general availability (GA) of deploying a VM Cluster running on a single VM for Oracle Exadata Database Service on Exascale Infrastructure (ExaDB-XS). Single VM support allows customers with smaller and lower availability needs the ability to avoid the cost and complexity of having a multi-node RAC cluster, instead having a single VM only, but still all the Oracle Real Application Clusters (Oracle RAC) software installed and running. VM Clusters can, therefore, be either permanently configured as a single node, or can be scaled back and forth from single node to multiple node VM Cluster configurations depending on workload and availability needs during a period of time.

Multiple Standby Databases

You can now create and manage multiple local and remote Oracle Data Guard standby databases linked to a primary database.

Release Date April.2025

This enhancement provides the ability to create and manage multiple local and remote standby databases linked to a primary database, providing flexibility for both data protection and disaster recovery. Local standby databases help minimize data loss, while remote standby databases safeguard against regional failures. This enhancement allows creation of up to 6 standby databases for a primary database.

In a typical Oracle Data Guard configuration, two standby databases are commonly used:

  • Local Standby: A standby database in the same region as the production database is ideal for failover scenarios, offering zero data loss for local failures (such as database, cluster, or availability domain failures). Application failover impact is reduced in this case, as applications continue operating without the performance overhead of communicating with a remote region.
  • Remote (Cross-Region) Standby: A remote standby database, located in a different region, is typically used for disaster recovery or to offload read-only query processing. A remote standby database setup ensures data protection against regional failures.

Some enterprise customers aim for symmetry after a site switch. For example, they may prefer to have both the primary and local standby in Region 1, and a remote standby with its own local standby in Region 2. In this configuration, there will be three standby databases. After a site switch, you will still have a primary database and a local standby readily available in the new primary region.

Additionally, customers can enhance their configurations by adding another standby database for testing purposes, leveraging our snapshot (read/write) standby capabilities.

Note

Creating a standby database associated with another standby database ("cascading standby") is not supported.