Re: exporting

I think Oracle should have chosen a different name for their directory objects within the database!

Apologies if the following is teaching granny to suck eggs....

Have you created a directory/folder on the OS? Does the oracle user have read/write access to it?

In the database, [probably] as SYS (Standard practice at my last few contracts) create a database directory pointing at your OS directory.

create directory backups as '/path/to/your/os/folder';

Then you need to give read and/or write permissions to the database user you will be running the export as. SYS already owns the directory object so is fine. Other users need permissions. In some contracts there was a backup_admin user created to do these things, so:

grant read,write on directory backups to backup_admin;

Now, when running expdp specify DIRECTORY=BACKUPS on the command line or in the parameter file.

If you need this (non SYS) user to be able to do a full export and/or import then you also need:

grant datapump_exp_full_database to backup_admin;

grant datapump_imp_full_database to backup_admin;

There's a whole load of hopefully easy to follow stuff on my blog at http://qdosmsq.dunbar-it.co.uk/blog/2013/08/introduction-to-oracle-datapump-part-1/ if you'll forgive the blatant plug! ;-)

HTH Cheers,
Norm.

On 25/02/16 23:46, Zelli, Brian wrote:
> Getting this error:
>
> ORA-39002: invalid operation
>
> ORA-39070: Unable to open the log file.
>
> ORA-39145: directory object parameter must be specified and non-null
>
> I created the directory file and gave rights to the user to write
> there. What am I missing?
>
> Brian

-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767
--
http://www.freelists.org/webpage/oracle-l