Oracle Cloud Infrastructure Documentation

Troubleshooting and Known Issues for Autonomous Database Services

Use the information in this section to resolve common errors and provisioning issues in your Oracle Database@Azure environments.

The issues covered in this guide do not cover general issues related to Oracle Database@Azure configuration, settings, and account setup. For more information on those topics, see Oracle Database@Azure Overview.

Troubleshooting Topics

Known Issues

Terminations and Microsoft Azure Locks for Autonomous Database Services

Oracle advises removal of all Microsoft Azure locks on Oracle Database@Azure resources before terminating an Autonomous Database Services resource.

For example, if you created a Microsoft Azure private endpoint, remove that resource first. If you have a policy that prevents the deletion of locked resources, the Oracle Database@Azure workflow will fail because Oracle Database@Azure cannot delete the lock.

IP Address Requirement Differences for Autonomous Database Services

There are IP address requirement differences between Oracle Database@Azure and Oracle Cloud Infrastructure (OCI).

  • Oracle Database@Azure reserves 13 IP addresses for the client subnet versus 3 for OCI requirements.

Maximum Transmission Unit (MTU) Differences for Autonomous Database Services

Maximum transmission unit (MTU) is the largest frame size (in bytes) that can be sent. It is a configurable setting.

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

Due to the differences in default MTU sizes, Path MTU Discovery (PMTUD) is required to determine the proper MTU between Azure resources and OCI services. For PMTUD to work, customers must allow Internet Control Message Protocol (ICMP) Type 3 code 4 on the entire network stack. Turning off ICMP completely can result in connectivity issues.

For more information, see the following:

Create Oracle Autonomous Database Serverless Workflow Contact List Disabled

When using the Create Oracle Autonomous Database Serverless workflow, the Contact List is disabled after entering an email address.

This happens if the email address entered has a '\' (backslash) character in the address string. Do not enter a '\' (backslash) character when entering email address.

Metrics Reporting Losses in Microsoft Azure

If any exporter sends a metric that is older than 20 minutes, the agents drops it and customers lose that data.

This 20 minute time-out is a limitation of Microsoft Azure, and applies to any exporter. For example, here are some scenarios where metrics may be lost.
  • Expired certificates: 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.
  • Exporter 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.
These are not an exhaustive list of examples, but are intended to provide context to metrics reporting loss.