On Unix, this really is an NFS issue and not Oracle or eHealth's issue. Some of the caching / refreshing of handles that NFS does causes RMAN to hang. Binary saves are not supported over NFS. However, you can do binary saves over NFS and it may work most of the time. In situations when a hang does occur, you may have to reboot the server / client machine to resolve the issue.
For Windows, remotely mounted shared drives are not supported for database saves.
eHealth RMAN database save issues with NFS and Windows shares
eHealth Oracle RMAN database hangs when writing to a NFS mount
eHealth Oracle RMAN database save fails when writing to a mapped network drive
When using RMAN to restore a database, where the RMAN backup is located on a remote node, this fails with errors like:
(In the example below H:\ is a mapped network drive).
RMAN-10035: exception raised in RPC: ORA-19505: failed to identify file "H:\BACKUP_RMAN\BACKUP15_RMAN1_432213015" ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 5) Permission denied.
At this time Concord is not aware of issues with ASCII saves and loads over NFS or Windows shares.
Causes of this problem:
The 'remote' RMAN file is being accessed by the Oracle process. On Windows, this process is the OracleService<SID> service. By default this service is started under the NT system account. This account however does not have privileges to access remote devices.
(Legacy KB ID CNC TS14617 )