Well I found the problem. Actually I had type error. I have typo "vahe.DMP" instead of "vahe.dmp"(in lower case ). I think error message is not good one, because it should clearly say that file does not exist instead of saying "unable to open dump file '' for read" (IMHO)
Impdp Unable To Open Dump File For Read [VERIFIED]
ORA-31640 Unable to open dump file "string" for readOracle Database Tips by Donald BurlesonNovember 18, 2015
Question: I am getting the ORA-31640 error during an import:
It looks like Oracle can't read the .dmp file, because it's under another user's home directory. Oracle has to be able to read it, not the Linux user you're running the impdp command as. (Contrary to my earlier misleading comments!)
If you dump file exceeds 5 TB, you can run the Oracle Data Pump export with the parallel option. This operation spreads the data into multiple dump files so that you do not exceed the 5 TB limit for individual files.
I have Oracle 11g R2 installed and SQL Developer. I am able to create a connection with the hr user. I followed some instructions on how to import via cmd with admin rights. All commands were fine until I pasted the path to where the dmp file is located and I get the error "failed to open for read". The path is correct and spelled correct with .dmp at the end. I am a lot further than I was a few months ago but still stuck. Does the dmp file need to be stored in a specific area? I read that error means, usually it is misspelled? I know it isn't corrupt but unsure of what I am doing wrong at this point. I posted the error I got (above) when I dimply tried to open the dmp file with sql developer, but again. I am not sure if more is needed before actually doing that?
Based on the information in the detailed error message, you can then resolve the issue. For example, if the dump file name already exists in DATA_PUMP_DIR, then the exception block gives an error similar to the following one:
b2a8ae9291