Oracle Cloud Infrastructure Documentation

Troubleshoot

Use the information in this section to resolve onboarding and cloud platform issues in your Oracle Database@Azure environments.

Purchasing Offers

  • Private offer isn't available in Azure Marketplace: The collection rule isn't enabled.

    Details: A private offer created for your organization by Oracle Sales is not displaying in Azure Marketplace.

    Error: The private products collection rule is not enabled in Azure Private Marketplace by the administrator of the Marketplace collection that is configured for the Azure subscription being used for Oracle Database@Azure. For more information, see Collections overview in the Azure documentation.

    Workaround: For instructions on enabling the private products collection rule, see Collection rules in the Azure documentation.

  • Private offer isn't available in Azure Marketplace: 3rd party services are not allowed for purchase.

    Details: A private offer created for your organization by Oracle Sales cannot be purchased in Azure Marketplace.

    Error: Azure Marketplace purchases are disabled by the administrator of a subscription being used for Oracle Database@Azure. Either all purchases are denied, or only Free/BYOL SKUs are allowed.

    Workaround: Have the subscription administrator enable the purchase of 3rd party services in Azure Marketplace. The Azure Marketplace authorization for the subscription must be "On", and can't be "Free/BYOL SKUs Only" or "Off". See Purchase control through EA billing administration under an Enterprise Agreement (EA) in the Azure documentation for more information.

  • Private offer can't be purchased in Azure Marketplace: "ResourceDeploymentFailure" error

    Details: When you attempt to purchase a private offer, you receive the following error because it reaches terminal provisioning state 'Failed'.

    Error: 
    "code": "ResourceDeploymentFailure","target":
      "/subscriptions/<AZURE_SUB_ID>/providers/Oracle.Database/oracleSubscriptions/default","message": "The resource write operation failed to complete successfully, because it
      reached terminal provisioning state 'Failed'."

    Cause: The private products collection rule is not enabled in Azure Private Marketplace by the administrator of the Marketplace collection that is configured for the Azure subscription being used for Oracle Database@Azure. For more information, see Collections overview.

    Workaround: For instructions on enabling the private products collection rule, see Collection rules.

  • Public Offer cannot link to an existing OCI subscription.

    Purchase Oracle Database@Azure via offer, aka Pay-as-you-go (PAYG), must create a new OCI Account for Oracle Database@Azure. Linking to an existing tenancy is only available through private offer.

  • Private offer can't be used with existing Pay As You Go (PAYG) tenancy

    When onboarding with a private offer, you can't link your Azure account to an OCI Pay As You Go (PAYG) tenancy. See Managing Account Upgrades and Payment Method for information on upgrading your account.

  • One purchase per Azure subscription.

    Each Azure subscription can only purchase one offer, either a private offer or public offer ( Pay-as-You-Go).

  • Change Plan Operations Returns Error

    Details: Error is returned when Change Plan option is selected.

    Error: Error messages are returned in the following situations:
    • "Error: Plan Change Not Available": You haven't received a confirmation from Oracle that your Oracle Database@Azure service is ready for a "change plan" update.
    • "Error: Plan Change Mismatch": You try to change the plan of a different Oracle Database@Azure service instance than the one you requested a change to through Oracle. This can happen if you have more than one Oracle Database@Azure service and you try to change the plan of a service that Oracle hasn't processed a "change plan" order for.
    Workaround:
    • "Error: Plan Change Not Available": Contact your Oracle Sales representative to confirm if your Oracle Database@Azure service instance is preprocessed for a change plan update. Include the Plan ID and Azure Subscription ID in your communication with Oracle Sales.
    • "Error: Plan Change Mismatch": Verify the plan ID and Azure Subscription ID with your Oracle Sales representative if needed. Then ensure you're using the plan ID and Azure Subscription ID that you shared with Oracle Sales, and try the operation again.
  • Unable to Purchase Private Offer Because Pay As You Go is in Plan Field

    Details: You are unable to purchase the private offer, as the Pay As You Go option is displayed on the purchase page instead.

    Solution: Navigate to the Sponsorship Portal and remove the credits from the Oracle Database@Azure offer. This will enable the private offer in the Plan field instead of Pay As You Go. Then, proceed with purchasing the private offer as described on the Purchase Offer page.

    Cause: Azure credits were used for the Oracle Database@Azure private offer, which is not allowed. Azure credits can only be applied to Azure products and cannot be used for products purchased through the Microsoft Azure Marketplace. For more information, please see Azure Credit Offer.

Onboarding

  • Onboarding fails because Azure OracleSubscription resource needs to be reset or deleted
    If you cannot onboard with Oracle Database@Azure because of a configuration problem with the OracleSubscription resource in Azure, Oracle Support can help you resolve the issue. This kind of problem can occur in the following types of scenarios:
    • The wrong billing ID was provided for a private offer.
    • The wrong OCI tenancy was linked to your Azure subscription.
    • The wrong private offer was purchased.
    • A public offer was purchased with an Azure subscription, and your organization wants to reuse the same Azure subscription to purchase a Private Offer.

    To reset or delete the OracleSubscription resource, you will need help from Oracle's Multicloud Support and Engineering team for all the scenarios described in this topic. Oracle will perform the actions listed in the following table, or assist you in performing them as appropriate. Open an Oracle Support Request (SR) to get help.. You can reference Knowledge Base article KB175725, which contains the information in this troubleshooting topic, in your Oracle Support Request.

    Table 1-1

    Scenario Actions performed by Oracle to resolve
    You no longer use the service.
    • In the OCI Console:: Delete DB home, PDB, and CDB
    • In the Azure Console: Delete Exadata and Autonomous Database resources
    • Delete the multicloud link
    • Delete the Azure subscription
    • Terminate the OCI Account (optional)
    The wrong billing ID was provided for a private offer.

    Correct the wrong billing ID for the CPQ quote and private offer.
    The wrong OCI tenancy was linked to your Azure subscription.

    Remove the multicloud link from the incorrect OCI tenancy so the account linking step can be performed again with the correct tenancy.
    The wrong private offer was purchased. Delete the OracleSubscription resource in Azure so a new OracleSubscription resource can be created and used to purchase the correct private offer.
    A public offer was purchased with an Azure subscription, and your organization wants to reuse the same Azure subscription to purchase a Private Offer.
    • In the OCI Console: Delete DB home, PDB, and CDB
    • In the Azure Console: Delete Exadata and Autonomous Database resources
    • Delete the multicloud link
    • Delete the Azure subscription
    • Terminate the OCI Account (optional)

Microsoft Azure Locks

  • Terminations and Microsoft Azure locks

    We recommend the removal of all Microsoft Azure locks to Oracle Database@Azure resources before terminating the resources. For example, if you're using a locked Microsoft Azure private endpoint with Oracle Database@Azure, confirm that the endpoint can be deleted, then remove the lock before deleting the Oracle Database@Azure resources. If you have a policy to prevent the deletion of locked resources, the Oracle Database@Azure work flow to delete system resources fails because Oracle Database@Azure can't delete a locked resource.

Networking

  • NSG cannot be applied to Azure delegated subnet on Default Network

    With the default network features in Azure, NSG rules cannot only be applied at the Azure delegated subnet for Oracle.

    Workaround:
    • Option 1: Keep the default network features in Azure but apply the NSG rules on OCI side (via VCN) instead of Azure side (via VNet).
    • Option 2: Register the following features to enable Advanced Network in Azure before creating a new delegated subnet for the Oracle Database@Azure, then apply NSG rules on Azure side.

    Table 1-2

    Feature Name Provider Namespace
    EnableRotterdamSdnApplianceForOracle Microsoft.Baremetal
    EnableRotterdamSdnApplianceForOracle Microsoft.Network
    Note

    • Wait until the status is 'Registered' before creating the delegated subnet.
    • As NSG rules are possible at both OCI and Azure side with Advanced Network feature enabled, make sure no conflicts between all security rules on both Azure and OCI side before apply. Misalignment of rules could lead to operational disruptions.
    • Refer to Microsoft documents for details.
  • Maximum number of delegated subnets
    • Each Azure Virtual Network (VNet) can contain maximum 1 delegated subnet for Oracle Database@Azure.
      • Multiple VM clusters from same Exadata Infrastructure are allowed in one delegated subnet.
      • Multiple VM clusters from different Exadata Infrastructure resources are allowed in one delegated subnet, as long as they are in the same availability zone.
      • Two Exadata Infrastructure resources (for example, a primary in availability zone 1, and a secondary located in availability zone 2) aren't allowed in one delegated subnet because this configuration would cause a sub-optimal network path.
    • Oracle Database@Azure service can use up to 5 delegated subnets, by default. If you need more delegated subnet capacity, you can request a service limit increase.
      • For information on viewing and increasing service limits in the OCI Console, see the following topics:
      • When submitting a service limit increase, note the following:
        • The service name is Multicloud.
        • The resource name is Delegated Subnet Multicloud Links.
        • The OCI service limit name for Oracle Database@Azure delegated subnets is azure-delegated-subnet-count.
        • The limit is applied at the regional level.
  • Enabling Advanced Networking for Azure Container Apps to Connect with Autonomous Database

    If a connection from Azure Container Apps to Autonomous Database is required, the Advanced Network feature must be enabled and a new Virtual Network (VNet) created.

  • VCN Flow Log Data Not Available in OCI Tenancy

    By default, OCI tenancies created during Oracle Database@Azure onboarding have a service limit of 0 (zero) for VNC Flow Logs. To use VCN Flow logs, request a service limits increase for your OCI tenancy. See To request a limit increase for VCN Flow Logs for instructions.

Error Conditions

  • Moving Azure subscription with Oracle Database@Azure to another Azure tenant

    Error message: "Moving an Azure subscription with an Oracle Database@Azure subscription resource to another azure tenant is currently not supported."

  • Error reason: Azure subscriptions that have been onboarded to Oracle Database@Azure can't be moved to another Azure tenant because the Oracle Database@Azure service would be interrupted.
  • Resolution: If you need to move an Azure subscription that has been onboarded with Oracle Database@Azure, open an Support Request with Oracle Support. Oracle's Multicloud Support team will help you with the request. See Oracle Database@Azure Support Information for details on opening a support request.

Prerequisites for the Azure East US 2 Region

If you onboarded with Oracle Database@Azure before April 15, 2025 and you want to use the Azure East US 2 region, you need to create policies in your OCI tenancy that allow you to create Oracle Database@Azure resources and use metrics in Azure East US 2. Use the instructions in this section to create policies for resources creation and metrics.

  • To enable resource creation in Azure East US 2

    Create the policy described in this section to enable resource creation in Azure East US 2. If you try to create resources to East US 2 without the required permissions, the Azure Portal displays the "Your deployment failed" message:

    Create the required policy as follows:

    1. Open the navigation menu, and select Identity & Security. From the Identity section, select Policies.
    2. Select Create Policy.
    3. Name: Enter Additional_Multicloud_Policy into the field.
    4. Description: It is an optional field. For example, you can enter Policy to enable Oracle Database@Azure resource creation in the Azure East US 2 region.
    5. In the Policy Builder, use the Show manual editor toggle switch to enable the manual policy editor field, then paste the following policy into the manual editor:
      define tenancy networking-dataplane2 as
        ocid1.tenancy.oc1..aaaaaaaailqy63b6fbqoa6jyd324iyb5xoafpji2j6evpqqx5or74vwknv5aendorse any-user to {DRG_ATTACHMENT_READ, DRG_ATTACH, DRG_DETACH, VCN_ATTACH,
        DRG_ROUTE_TABLE_ATTACH, ROUTE_TABLE_ATTACH, ROUTE_TABLE_DETACH} in tenancy
        networking-dataplane2 where all { request.principal.type = 'multicloudlink' }
    6. Select the Create button to create the policy. The new policy is listed in the Policies list view page.
    Note

    If you onboarded with Oracle Database@Azure on or after 15th April 2025, no action is required.
  • To enable observability (metrics) in Azure East US 2
    Create the required policy for observability (metrics) as follows:
    1. Open the navigation menu, and select Identity & Security. From the Identity section, select Policies.
    2. Select Create Policy.
    3. Name: Enter Additional_Observabilioty_Multicloud_Policy into the field.
    4. Description: It is an optional field. For example, you can enter Policy to enable Oracle Database@Azure metrics for Azure East US 2 region.
    5. In the Policy Builder, use the Show manual editor toggle switch to enable the manual policy editor field, then paste the following policy into the manual editor:
      define tenancy obs_tenancy_2 as
        ocid1.tenancy.oc1..aaaaaaaalfamrkmvchwc3mndr4c4htwtntx2ampbas3z42c6sxyqviit4gtadefine tenancy obs_cp_tenancy_2 as
        ocid1.tenancy.oc1..aaaaaaaa7bzfp55yuik3t2sesnqgsyohpbfr4ocl4vlq7foyhmaa34xktyjaendorse any-user to use stream-push in tenancy obs_tenancy_2 where all {
        request.principal.type='multicloudlink' }endorse any-user to read streams in tenancy obs_tenancy_2 where all {
        request.principal.type='multicloudlink' }admit any-user of tenancy obs_tenancy_2 to use metrics in compartment id
        ocid1.compartment.oc1..aaaaaaaalro4yg4evjyyrtxrjedakvtg6tcqizdg4xulwbcxctwtpc3nvjdq where
        all {request.principal.type='serviceconnector'}admit any-user of tenancy obs_cp_tenancy_2 to { DATABASE_INSPECT,
        PLUGGABLE_DATABASE_INSPECT } in compartment id
        ocid1.compartment.oc1..aaaaaaaalro4yg4evjyyrtxrjedakvtg6tcqizdg4xulwbcxctwtpc3nvjdq where
        all { request.principal.type = 'workload', request.principal.namespace = 'obs-cp', request.principal.service_account =
    'obs-cp-service-account’}
    6. Select the Create button to create the policy. The new policy is listed in the Policies list view page.
    Note

    If you onboarded with Oracle Database@Azure on or after 15th April 2025, no action is required.