Unable To Create Dump file | ORA-39001,ORA-39000,ORA-31641,ORA-27054

Error Details:
*****************

Export: Release 11.2.0.3.0 - Production on Sat Apr 29 15:00:44 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/mount-mig/TT0037598650/fullpserv_01.dmp"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
Additional information: 18


Solution Description:
**************************
Mostly you will get this error on SunOS:
----------------------------------------------------
Start The Database And Run This : sqlplus / as sysdba

ALTER SYSTEM SET EVENTS '10298 trace name context forever, level 32'; 

Datapump Import (IMPDP) fails due to Error ORA-31693,ORA-31640,ORA-19505,ORA-27037

Error Details:
*****************

ORA-31693: Table data object "VERTEX"."RATECITY" failed to load/unload and is being skipped due to error:
ORA-31640: unable to open dump file "/mnt/vertex/importdata/expdp_fulldb_vert/expdp_fulldb_vertppf_19082017_02.dmp" for read
ORA-19505: failed to identify file "/mnt/vertex/importdata/expdp_fulldb_vert/expdp_fulldb_vertppf_19082017_02.dmp"
ORA-27037: unable to obtain file status

Solution Description:
**************************

Issue is due to the mount/file system was not being accessible from the second node.
Then use Cluster=N to force Data Pump to use only the instance where the job is started and ran again data pump job using below datapump parameter:

Cluster=N