EXPDP Error on 10.2.0.4

Question

Hello,
Oracle DB 10.2.0.4
Windows 2003R2
I am getting below error:
C:\WINDOWS>expdp system/******* full=y estimate_only=y
Export: Release 10.2.0.4.0 - 64bit Production on Thursday, 21 February, 2013 0:2
4:27
Copyright (c) 2003, 2007, Oracle.  All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing 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 488
ORA-29283: invalid file operationEven with the SYS user, I am getting same error.
I have even re-installed data-pump on this database, but with no luck!
Kindly advice.
Thanks,
Suddhasatwa

Answer 1

Hi,
LOGFILE
Default: import.log
Purpose
Specifies the name, and optionally, a directory object, for the log file of the import job.
Syntax and Description
LOGFILE=[directory_object:]file_name
If you specify a directory_object, it must be one that was previously established by the DBA and that you have access to. This overrides the directory object specified with the DIRECTORY parameter. The default behavior is to create import.log in the directory referenced by the directory object specified in the DIRECTORY parameter.
If the file_name you specify already exists, it will be overwritten.
All messages regarding work in progress, work completed, and errors encountered are written to the log file. (For a real-time status of the job, use the STATUS command in interactive mode.)
+_A log file is always created unless the NOLOGFILE parameter is specified. As with the dump file set, the log file is relative to the server and not the client._+Note:
Data Pump Import writes the log file using the database character set. If your client NLS_LANG environment sets up a different client character set from the database character set, then it is possible that table names may be different in the log file than they are when displayed on the client output screen.
Example
The following is an example of using the LOGFILE parameter. You can create the expfull.dmp dump file used in this example by running the example provided for the Export FULL parameter. See FULL.
impdp hr/hr SCHEMAS=HR DIRECTORY=dpump_dir2 LOGFILE=imp.log DUMPFILE=dpump_dir1:expfull.dmp
Because no directory object is specified on the LOGFILE parameter, the log file is written to the directory object specified on the DIRECTORY parameter.Edited by: Chanchal Wankhade on Feb 20, 2013 10:22 PM