ORA-31693 & amp; ORA-31640 & amp; ORA-19505 & amp; ORA-27037 & amp; impdpora-31693

Impdp when encountering ORA-31693 & ORA-31640 & ORA-19505 & ORA-27037, impdpora-31693
ORA-31693 & ORA-31640 & ORA-19505 & ORA-27037
An error occurred during impdp:
Additional information: 3
.. Imported "HQ_X1". "T_XX130901": "SP15" 13.99 KB 0 rows
.. Imported "HQ_X1". "T_XX130901": "SP2" 13.99 KB 0 rows
ORA-31693: The table data object "HQ_X1". "TEMP_YEAR_MONTH" cannot be loaded/uninstalled and skipped. The error is as follows:
ORA-31640: Unable to open the dump file to read "/HQ_X22.DMP"
ORA-19505: unrecognized file "/HQ_X22.DMP"
ORA-27037: Unable to get File status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
My impdp command:
Nohup impdp HQ_X1/HQ_X1 DUMPFILE = HQ_X1 % u. DMP transform = oid: n DIRECTORY = dir1 parallel = 8 &
I read the official documents:
The causage of this problem has been identified in unpublished bug 9378256. it is caused by a RAC instance not having physical access to the dump file (as indicated by the DIRECTORY parameter) and using a parallel degree> 1. the problem with this setup is that the PQ/PX slaves are not constrained to the RAC instance from which the IMPDP operation has been started, and when such a PQ/PX slave doesn't have access to the dump file, the errors are raised.
The behavior is also reported in unpublished Bug 8415620-DATA PUMP DOES NOT HONOR THE BOUNDARIES OF THE CONNECTED SERVICE ON RAC
DataPump RAC support is provided in 11.2. prior to 11.2, once you use a service to make the initial connection to the database, an instance is selected and the master process and all worker processes run on that instance.
In 11.2, the new DataPump parameter CLUSTER is introduced:
Syntax and Description: CLUSTER = [Y | N]
CLUSTER: Default = Y
Purpose:
Determines whether Data Pump can use Oracle Real Application Clusters (RAC)
Resources and start workers on other Oracle RAC instances.

The issue has been fixed in the 11.2.0.2 patchset.
Possible workarounds for the 11.2.0.1 release are:
Use the CLUSTER or SERVICE_NAME parameters to constrain the IMPDP job never to run on the instance not having access to the dump file
Configure the database parameters in such a way that PQ/PX slaves are never started on the instance not having access to the dump file
Use the PARALLEL = 1 IMPDP command line parameter to disable parallel functionality during import
Store all dump files on a local filesystem of one of the RAC nodes and use a parallel degree lower than the number of dump files and import with the CLUSTER = N command line option
Mount the cluster filesystem on all nodes and set the parallel degree to be equal to the number of dump files and import with the CLUSTER = N command line option
Add cluster = N to solve the problem:
Nohup impdp HQ_X1/HQ_X1 DUMPFILE = HQ_X1 % u. DMP transform = oid: n DIRECTORY = dir1 parallel = 8 cluster = n &
Compared with exp/imp, expdp/impdp has many bugs.