23 comments
  1. Tim Hall said:

    I’ve seen this a number of times over the years with Oracle on Windows. Never seen it on Linux or UNIX. Solution: Don’t use Windows. :)

    Cheers

    Tim…

  2. Totally agree. Just encountered some performance problems, for which the problem would have been found a few weeks earlier if it would be on linux, because diagnostic tools are part of the distribution (and known, at least to me)

    Oracle is doing its thing with waiting for the Windows version with 11gr2 for quite some time now. ;-)

  3. Ivan Kartik said:

    Good point Tim. Totally agree :-D

    • I was (and am) using a local administrator account for the database services. Because local administrators does not get rights on shares, it fails.
      My resolution in this case was to use UNC naming for a share. The share allowed guest writes, which is why using UNC naming works.
      If the share requires credentials, using a domain account will take care of that (because it’s the local administrator which has no rights).

  4. sqlplus said:

    If you use an unc-Path as directory e.g.
    create direcotoy my_dumps ‘\\server5\share2\dir1\’;
    the expdp works fine;
    BE SURE that the share has write access to everyone , because Oracle.exe runs as SYSTEM under MS-Servers.
    I testet it today on an Oracle11g 64Bit OS W2k8R2 ;

  5. rajasekaran said:

    WINDOWS SYSTEM

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir1 as ‘\\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir1 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir dumpfile=odst schemas=odst logfile=
    odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:06:09

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir1 as ‘\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir1 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir dumpfile=odst schemas=odst logfile=
    odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:07:13

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir2 as ‘v:\\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir1 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir dumpfile=odst schemas=odst logfile=
    odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:07:50

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir3 as ‘v:\10.86.24.151\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir1 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir dumpfile=odst schemas=odst logfile=
    odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:08:58

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir2 as ‘v:\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir2 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir2 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:09:28

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir3 as ‘v:\\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir3 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir3 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:09:51

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir4 as ‘\\10.86.24.151\dba\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir4 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir4 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:10:18

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir5 as ‘\\10.86.24.151\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir5 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir5 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:14:56

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir6 as ‘v:\10.86.24.151\test’;

    Directory created.

    SQL> grant read,write on directory expdpdir6 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir6 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:15:25

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir7 as ‘v:\10.86.24.151\test\’;

    Directory created.

    SQL> grant read,write on directory expdpdir7 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir7 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:15:56

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL> create or replace directory expdpdir8 as ‘\\10.86.24.151\test\’;

    Directory created.

    SQL> grant read,write on directory expdpdir8 to system,odst;

    Grant succeeded.

    SQL> host expdp odst/odst directory=expdpdir8 dumpfile=odst schemas=odst logfile
    =odst.log

    Export: Release 10.2.0.3.0 – Production on Tuesday, 14 December, 2010 21:17:42

    Copyright (c) 2003, 2005, Oracle. All rights reserved.

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Produc
    tion
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at “SYS.UTL_FILE”, line 475
    ORA-29283: invalid file operation

    SQL>

    SAME ERROR. PLEASE HELP ME

    • This is because of rights on the windows/operating system level see MOS:

      Unable to Export to a Mapped Network Drive Using DataPump (Doc ID 428130.1)

  6. Harry Schreurs said:

    Frits,

    I just managed to to make a dumpfile using expdp on a mapped drive.
    If you are interested, then let me know and I will give you the nitty-gritty details.

    Kind regards,

    • Harry, I am very interested! But please bear in mind that in most situations the possibilities are limited because it’s client’s systems I work on.

    • Jeff Dietz said:

      Hey, came upon your entry for dumpfile/directory for expdp using a mapped drive – can I request the ‘nitty-grity’ details?
      Thanks in advance – Jeff Dietz

  7. Eric said:

    Please let me know too …

  8. Igor said:

    still no details?

  9. Laurens said:

    Same problem here passwordless share not an option. Longing for nitty gritty details.
    @Frits did you get more info ?

    • I did not get more information, which is the reason I did not answer any of the following ‘Please let me know too’.
      Did you have a chance to look at MOS 428130.1? The limitations and reasons for the rejection to write are quite well explained.

      • Laurens said:

        Yes looked at that and others, however running databases on another account is not allowed at the customer. Thx for the suggestion.

  10. Another reasonably simple resolution is to allow everybody to write on the share.

    A bit more far-fetched resolution for getting a windows data pump result in another place would be to use iSCSI instead of a share for placing a file or files on a remote place. If you want even more effort all kinds work-arounds (not real solutions) can be thought of: rsync, NFS (there are windows NFS clients).

  11. Laurens said:

    As stated passwordless share is not an option. Already looked at other solutions however we have a lot of limitations:
    -Not enough local storage to store data of full database export (before rsync)
    -Windows machines may not be changed (on AIX we used nfs, which is not allowed for windows) ?
    -A lot of databases will be transfered (to Exadata) about 175 currently running on windows so looking for an easy to implement solution (more time effort spending setting it up once and less time using it).
    -Databases should be transfered as fast as possible so we prevent the use of intermediate systems and write directly to Sun ZFS appliance wich is connected to the database systems.

  12. Hi Laurens, not sure if we met before (I have a very weak memory for both names and faces), I know a thing or two about Exadata ;-)

    As far as I know, windows server does not support NFS. I don’t know anything about 3rd party NFS clients. A quick search reveals Windows 7 and very recent windows server seem to have NFS support, again: I don’t know.

    With this limitations, have you thought about using the option to use datapump through a database link? This would bypass the usage of any storage in between source and destination database.

    It all depends on very much details, but 175 databases with a normal configuration are not going to fit on an Exadata, even a full rack (even if all databases would not use RAC)?

    • Laurens said:

      We probably have met before (however maybe I just remember your name, rather known in the Netherlands for Dutch DBA’s). Maybe on 11 december on the Ogh meeting (I’m not sure yet if I’ll be there).
      -Windows still doesn’t support NFS, there are clients however not allowed
      -Through a database link maybe a solution but involves work for each database
      -We have 4 Exadata rack’s now, will be 6 ones.

  13. The essence is there needs to be a concession somewhere.

    I don’t know the ZFS appliance intimately (yet), another creative (potential) resolution is to alter the firewall for SMB (windows shares) access to allow only the windows databases servers, and enable world write access, so it’s limited to the database servers, which can write then.

    You go from probably filesystem based databases to ASM. You probably want to change parameters. You probably want to limit the number of tablespaces. You probably want bigfile tablespaces, etc. This means there always is per database work involved. In my opinion going to Exadata without any modification does not make sense.

    • Laurens said:

      CIFS (see http://docs.oracle.com/cd/E19082-01/820-2429/6ne1idad5/index.html) is used. I also don’t know what IP filtering possibilities ZFS appliance has, I’ll ask the guys who manage the systems

      Yep filesystems to ASM with BIGFILES. Single Node to RAC and 10g to 11gR2. However we want to put the effort on the destination (Exadata) and not the source (Windows). The Windows environment doesn’t have any slack.

      p.s. We can discuss this further on Linked in, I send you an Invite.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 2,191 other followers

%d bloggers like this: