This content has been marked as final. Show 8 replies
Why don't you directly import on local machine using network_link or you need dumpfile for some other reasons.
I do not to import on local side, i just want to keep daily dmp file which about 50GB, to save disk space on production side.
You should just be able to use NETWORK_LINK=remote_db and directory=local_directory.
See an example here: http://www.oracle-base.com/articles/10g/oracle-data-pump-10g.php
You may have to make the local directory name different from any in the remote db to avoid datapump getting confused.
Following errors come
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-39087: directory name DP_DIR is invalid
If you run expdp on machine A, then the dump file will be on machine A. If you specify a network_link that points to machine B, the that is where the ddl and XML source will come from. Your directory object needs to be defined on machine A that points to a directory on machine A.
We do this all the time.
Hope this helps.
So, i conclude from this discussion, that it is not possible to create dump file on local drive.
No it does work.
perhaps you don't have permissions on the local directory?
by default all directories are owned by sys and 'normal' users to not have permissions.
grant all on directory xxx to user;
where xxx is your local oracle directory and user is the user you are running expdp as.
You conclusion is not correct. You said that you wanted to create the dumpfile on machine A, but get the data and metadata from machine b. In this case,you can, and the dumpfile will be on machine a.
I guess it depends on what you are defining as your 'local' machine. If it is a, then yes, if it is b, then no.