0

why am I encountering this error when executing impdp command?

My command looks like this:

impdp directory=dp_dir dumpfile=testdb.dmp logfile=testdb.log

Error message:

ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation

closed as off-topic by Philᵀᴹ, dezso, RLF, Andriy M, Balazs Papp Sep 30 '16 at 19:13

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Philᵀᴹ, dezso, RLF, Andriy M, Balazs Papp
If this question can be reworded to fit the rules in the help center, please edit the question.

2

One way to find the cause of ORA errors is to use oerr tool by Oracle. In the error stack the top most is the application error which is followed by other secondary errors.

For example, the ORA-39002 and ORA-39070 are Datapump errors. Lets see what the oerr tool says for ORA-39070.

[oracle@localhost ~]$ oerr ORA 39070
39070, 00000, "Unable to open the log file."

Cause: Errors were detecting while opening the log file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

The action is to fix the problem outlined by the secondary error message that is ORA-29283.

[oracle@localhost ~]$ oerr ORA 29283
29283, 00000, "invalid file operation"

Cause: An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system.

Action: Verify file and directory access privileges on the file system, and if reading, verify that the file exists.

And that's it.

0

My problem has been fixed. I just executed

chmod -R 777 <my_data_pump_folder>

Seems that I don't have the privilege to write in <my_data_pump_folder>

  • 2
    As far as the OS is concerned, the one asking to do I/O in that directory is the OS user that started the oracle db. That would normally be "oracle". So instead of the overly-permissive '777', the permissions really don't need to be any more than 700 or 770, with the directory owned by oracle;oinstall or oracle:dba – EdStevens Sep 30 '16 at 12:35

Not the answer you're looking for? Browse other questions tagged or ask your own question.