RAC Impdp ORA-31693, ORA-29913, ORA-31640, ORA-19505, ORA-27037 fixing problems

1.PURPOSE AND SCOPE

If  the dumpfile located on non-shared area and  dba try to start impdp operation with parallel on RAC servers (version 11gR2),dba would receive  ORA-31693, ORA-29913, ORA-31640, ORA-19505, ORA-27037 errors. The reason behind it oracle try to import using all RAC nodes for this operation and if the dumpfile is located on non-shared place , it could no reach it.

2.PRACTICE

2.1. Starting impdp operation.

$ impdp bcanbakal/bcanbakal directory=exp parallel=8 dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y 

ORA-31693: Table data object "ESK"."FPP_WALT_MATCH" failed to load/unload and is being skipped due to error:
ORA-31640: unable to open dump file "/u01/app/exp/schmedump_08.dmp" for read
ORA-19505: failed to identify file "/u01/app/exp/schmedump_08.dmp"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

2.2. We can solve this problem with 3 ways.

2.2.1. We can move dump file to shared location like ASM.

2.2.2. We can add CLUSTER=N parameter so only one node would execute this import operation.

$ impdp bcanbakal/bcanbakal directory=exp parallel=8 dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y CLUSTER=N

2.2.3. When we parallel parameter oracle automaticly use CLUSTER=YES parameter at import operation so if you remove parallel parameter on impdp operation there wont be any issue..

$ impdp bcanbakal/bcanbakal directory=exp  dumpfile=schmedump_%U.dmp logfile=log:impdp.log full=y