expdp error : ORA-31617: unable to open dump file "/backup/salesdb_backup_02.dmp" for write ORA-19505: failed to identify file "/backup/nightly_backup/salesdb_backup_02.dmp" ORA-27037: unable to obtain file status

expdp parfile=params

content of params.sh:
userid=scott/tiger
parallel=2
.
.
.
ORA-31693: Table data object "HR"."EMP" failed to load/unload and is being skipped due to error:
ORA-31617: unable to open dump file "/backup/salesdb_backup_02.dmp" for write
ORA-19505: failed to identify file "/backup/nightly_backup/salesdb_backup_02.dmp"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

Remedy in 11g is use parameter cluster=N

This error occures when parallel parameter is specified in using expdp in RAC databases  and same physical directories does not exists in all nodes. This error is fixed in 11g only using cluster=N

ORA-31633: unable to create master table "SYSTEM.NIGHTLY_EXPORT"

expdp  parfile=params

content of params:
userid=system/manager
job_name=nightly_export.
.
.
.
[This will create a table with NIGHTLY_EXPORT in system schema or from the schema from which the expdp command is run]

Export: Release 11.2.0.3.0 - Production on Wed Sep 18 08:57:30 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORA-31626: job does not exist
ORA-31633: unable to create master table "SYSTEM.NIGHTLY_EXPORT"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1020
ORA-00955: name is already used by an existing object

This error comes when expdp job with the specified parameter job_name is already existing. It could be the case 1) expdp job is attempted to start with given job_name while expdp job with the same job_name is already running 2) expdp job with given job_name is currently not executing but it was previously stopped or cancelled.

Remedy: Verify from querying DBA_DATAPUMP_JOBS that job with specified job_name is not running then drop the table SYSTEM.NIGHTLY_EXPORT as in given example.