Oracle Exadata Database Service on Dedicated Infrastructure

Error returned by CreateCloudVmCluster operation in Database service. (400, InvalidParameter, false) domain name cannot contain more than 4 labels

404 NotAuthorizedOrNotFound

Allow any user to use tag-namespaces in tenancy where request.principal.type = ‘multicloudlink’
Allow any user to manage tag-defaults in tenancy where request.principal.type = ‘multicloudlink’

• Oracle AI Database@Azure only supports Exadata X9M. All other shapes are unsupported.
• Oracle AI Database@Azure reserves 13 IP addresses for the client subnet versus 3 for OCI requirements.

• Azure default MTU size = 1500 bytes
• OCI default MTU size = 9000 bytes

• TCP/IP performance tuning for Azure VMs
• Path MTU Discovery
• Internet Control Message Protocol

Authorization Failed
The client <client_name> with object id <object_id> does not have authorization to perform action 'Oracle.Database/location/operationStatuses/read' over scope <scope_details> or scope is invalid. If access was recently granted, please refresh your credentials.

1. Ensure that no Azure policy assigned to the user or the subscription is preventing the user from performing the action. If the user has specific permissions assigned to them directly, add the following resources to the authorized list.
   • Microsoft.BareMetal/BareMetalConnections
   • Microsoft.Network/privateDnsZones
2. Delete the failed Exadata VM Cluster from the Azure UI.
3. Wait 30 minutes to ensure that the Exadata VM Cluster is fully terminated in both Azure and OCI. This wait period ensures that all dependent resources are also deleted.
4. Provision your new Exadata VM Cluster.

Cannot delete Exadata infrastructure. All associated VM clusters must be deleted before you delete the Exadata infrastructure. (Code: 400)

Error returned by CreateCloudVmCluster operation in Database service.(400, InvalidParameter, false) Cidr block of the subnet must have at least 11 ip addresses available.

• Certificates expired. Exporter cannot establish connection with agent and a backlog of metrics builds. After rotating to new certificates, the metrics are stale and because they are more than 20 minutes old, the agent drops the metrics and customers will see these metrics.
• Backlog: When the exporter, for any reason, develops a backlog that results in the exporter taking longer than usual to process the metrics, metric will be lost if they are received by the agent more than 20 minutes old.

(Code: ResourceMoveProviderValidationFailed) Resource provider 'Oracle.Database' failed to process resource move validation for resource type '<RESOURCE_TYPE>'

# domain domain 1.oraclevcn.com domain2.oraclevcn.com localdomain
nameserver 169.254.169.254
#### END Generated by Exadata ####

• Database Server Type
• Storage Server Type

resource "azurerm_oracle_exadata_infrastructure" "example" {
 name                 = "example-exadata-infra"
 resource_group_name  = azurerm_resource_group.example.name
 location             = azurerm_resource_group.example.location
 zones                = ["1"]
 display_name         = "example-exadata-infra"
 storage_count        = 3
 compute_count        = 2
 shape                = "Exadata.X11M"
 database_server_type = "X11M"
 storage_server_type  = "X11M-HC"

1. To view the list of valid timezones, see Exadata Timezone Settings .
2. Ensure the correct timezone is defined in the Terraform code. For example:

   
   body = {
    "properties": {
        ...
        "timeZone": "<TIMEZONE>",
   
   

VM_CLUSTER_CREATE_FAILED

Error occurred when executing createVmCluster workflow: Error returned by
      CreateCloudVmCluster operation in Database service.(400, InvalidParameter, false) Each domain
      name label label can contain only letters and numbers.