ZDM Physical Offline migration can use an Azure Files NFS share as the common location for RMAN backup files. Because the NFS share is mounted on both the source and target database hosts, file ownership must be interpreted consistently on both systems.

NFS using Unix-style permissions identifies users primarily by their numeric UID rather than simply by the textual account name. Oracle's ZDM migration guidance explicitly states that the NFS-mounted path is readable by the target database user only when the source database user's UID matches the target database user's UID. Thus, two hosts can both have an account named oracle, but if those accounts have different numeric UIDs, files created by one host can appear to be owned by a different identity on the other.

Port 443 and SQL*Net listener port 1521 address network/API or database-client connectivity; neither resolves Unix file ownership on an NFS mount. Active Directory Domain Services authentication is likewise not the controlling permission model for the documented NFS migration workflow.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Physical Offline migration, Azure Files NFS, RMAN backup staging and Linux UID permissions.

===============