Azure Availability Zone Mapping For Oracle Database@Azure
Learn how to find the Azure availability zone mapping that controls the physical locations of your Azure subscription’s availability zones.
In the Azure portal, the zone displayed for your selected region is considered the logical zone. The logical zone isn't necessarily in the same physical zone. For example, in the East US region in your subscription, the logical zone named "zone 1" isn't necessarily the "eastus-az1" physical zone.
Mapping can differ between subscriptions, as shown in this example:
Azure Subscription | Logical Zone | Physical Zone |
---|---|---|
Subscription A |
East US AZ 1 |
eastus-az1 |
Subscription B |
East US AZ 1 |
eastus-az3 |
In Azure, a logical zone is mapped to a physical zone as described in Azure document Physical and logical availability zones.
When planning an Exadata deployment, you need to ensure that you have the correct limits set for the availability zone you're using. You also need to know the physical location of the availability zone to ensure that your hardware is provisioned in the physical location that works best for your applications and resources. For information on increasing your Oracle Database@Azure service limits, see Requesting a Limit Increase for Database Resources.
Using the Azure Cloud Shell or CLI, you can find the mapping between physical and logical Azure availability zones in your Azure subscription. Both Azure and OCI randomize the mapping of physical and logical availability zones, and therefore the physical location of a logical zone can differ between Azure subscriptions.
Before you begin:
You need the following information to run the Azure CLI command in this topic:
- The Azure subscription ID for the subscription you're using. To find this in the Azure console, see Get subscription and tenant IDs in the Azure portal.
-
The Name of the Azure region you are mapping. For example, the Azure region with the Display Name "Germany West Central" has the Name
germanywestcentral
. For the CLI command discussed in this topic, you would use the stringgermanywestcentral
in the command to find the availability zone mapping for the Germany West Central region.To find the Names of all Azure regions, you can run the account list-locations CLI command, as follows:
az account list-locations -o table
The output is formatted as shown in the example table that follows . The "Name" value needed for this topic is shown in the second column in the table.
DisplayName Name RegionalDisplayName ------------------------ ------------------- ------------------------------------- East US eastus (US) East US UK South uksouth (Europe) UK South Central India centralindia (Asia Pacific) Central India Germany West Central germanywestcentral (Europe) Germany West Central ... ...
-
Open the Azure Cloud Shell or CLI. You can open Cloud Shell by select the Cloud Shell icon from the top navigation of the Azure portal:
Use the PowerShell option to run the command in this task. See What is Azure Cloud Shell for more information.
-
Run the following command to find the mapping:
az rest --method get --uri '/subscriptions/{subscriptionId}/locations?api-version=2022-12-01' --query 'value' |jq -c '[ .[] | select( .name == "{regionName}")]' | jq
To run the command, you must replace the variables shown in brackets "{}", as follows. Don't include the brackets when you enter the actual values for these variables:
subscriptionId
: Your Azure subscription ID.regionName
: This value represents the Azure region'sName
value, discussed earlier in this topic under Before you begin. Don't use the "DisplayName" or the "RegionalDisplayName" for this value.
Example command:
az rest --method get --uri '/subscriptions/00000000-0000-0000-0000-000000000000/locations?api-version=2022-12-01' --query 'value' |jq -c '[ .[] | select( .name == "eastus")]' | jq
Example output:
[ { "availabilityZoneMappings": [ { "logicalZone": "1", "physicalZone": "eastus-az2" }, { "logicalZone": "2", "physicalZone": "eastus-az3" }, { "logicalZone": "3", "physicalZone": "eastus-az1" } ], "displayName": "East US", "id": "/subscriptions/<subscription-id>/locations/eastus", "metadata": { "geography": "United States", "geographyGroup": "US", "latitude": "37.3719", "longitude": "-79.8164", "pairedRegion": [ { "id": "/subscriptions/<subscription-id>/locations/westus", "name": "westus" } ], "physicalLocation": "Virginia", "regionCategory": "Recommended", "regionType": "Physical" }, "name": "eastus", "regionalDisplayName": "(US) East US", "type": "Region" } ]
OCI Availability Domain Mapping
OCI regions have availability domains, which are similar to Azure's availability zones. As in Azure, OCI provides a numbered logical availability domain (AD) name for your tenancy that doesn't necessarily match the numbering of the corresponding physical AD.
Mapping can differ between OCI tenancies, as shown in this example:
OCI Tenancy | Logical AD | Physical AD |
---|---|---|
Tenancy A |
US East (Ashburn) AD 1 |
us-ashburn-1-ad-3 |
Tenancy B |
US East (Ashburn) AD 1 |
us-ashburn-1-ad-1 |
To get the mapping details for your Oracle Database@Azure OCI tenancy, Create a service request with Oracle Support.
See Your Tenancy's Availability Domain Names in the OCI documentation for more information on availability domain names in OCI.
Azure to OCI Physical Data Center Mapping
Expand the "Physical Data Center Mapping" section that follows to see a table mapping physical Azure availability zones to physical OCI availability domains. See "OCI Oracle Database@Azure - How to determine physical location of OCI Availability Domains and Azure Availability Zones" (KB174336) in the My Oracle Cloud Support Knowledge Base for more information.
Geographic Location | Physical Azure AZ | Physical OCI AD |
---|---|---|
North America | canadacentral-az2 | ca-toronto-1-ad-1 |
North America | canadacentral-az3 | ca-toronto-1-ad-1 |
North America | centralus-az1 | us-chicago-1-ad-1 |
North America | centralus-az2 | us-chicago-1-ad-2 |
North America | eastus-az1 | us-ashburn-1-ad-1 |
North America | eastus-az3 | us-ashburn-1-ad-3 |
North America | eastus2-az3 | iad-ad-2 |
North America | eastus2-az2 | iad-ad-1 |
North America | westus (no AZs in region) | us-sanjose-1-ad-1 |
EMEA | uksouth-az1 | uk-london-1-ad-2 |
EMEA | uksouth-az2 | uk-london-1-ad-1 |
EMEA | ukwest (no AZs in region) | uk-cardiff-1-ad-1 |
EMEA | francecentral-az2 | eu-paris-1-ad-1 |
EMEA | francecentral-az3 | eu-paris-1-ad-1 |
EMEA | germanywestcentral-az3 | eu-frankfurt-1-ad-3 |
EMEA | germanywestcentral-az2 | eu-frankfurt-1-ad-1 |
EMEA | italynorth-az2 | eu-milan-1-ad-1 |
EMEA | italynorth-az1 | eu-milan-1-ad-1 |
APAC | australiaeast-az3 | ap-sydney-1-ad-1 |
APAC | australiaeast-az2 | ap-sydney-1-ad-1 |
APAC | australiasoutheast (no AZs in region) | ap-melbourne-1-ad-1 |
APAC | japaneast-az2 | ap-tokyo-1-ad-1 |
APAC | japaneast-az3 | ap-tokyo-1-ad-1 |
APAC | southeastasia-az1 | ap-singapore-1-ad-1 |
APAC | southeastasia-az2 | ap-singapore-1-ad-1 |
LAD | brazilsouth-az2 | sa-vinhedo-1-ad-1 |
LAD | brazilsouth-az3 | sa-vinhedo-1-ad-1 |