Error: ORA-27054: NFS File System Is Not Mounted With Correct Options

Issue

Connections fail at the Validating access to redo log setup test. The following errors appear:

• ORA-19504: failed to create file
• ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

Environment

• Connector: Oracle
• Automatic Storage Management (ASM)
• Staging directory on Azure Blob Storage (NFS 3.0)

Resolution

To resolve this issue, move the ASM staging directory to local block storage on the database virtual machine (VM). This is the preferred option because it avoids NFS compatibility issues and provides better performance.

Alternatively, if you must use network storage, move the staging directory to Azure NetApp Files or Azure Files (NFS 4.1). These services support the NFS mount options required by Oracle.

After moving the ASM staging directory to a supported storage location, update the staging directory path in Fivetran:

1. Go to your Oracle connection page.
2. Select the Settings tab.
3. Click Edit connection.
4. In the ASM Staging Directory Path field, enter the new path.
5. Click Save & Test.

For more information, see the Microsoft documentation on known issues with NFS 3.0 protocol support for Azure Blob Storage.

Cause

This issue occurs when the ASM Staging Directory Path you provide points to Azure Blob Storage using NFS 3.0. Oracle requires hard mounts and Network Lock Manager (NLM) support. Azure Blob Storage NFS 3.0 doesn't support the required locking and transactional semantics, so Oracle can't write to the mount, resulting in the above error.