Specifies the name, and optionally, a directory, for the log file of the export job.
Syntax and Description
You can specify a database
directory_object previously established by the DBA, assuming that you have access to it. This overrides the directory object specified with the
file_name specifies a name for the log file. The default behavior is to create a file named
log in the directory referenced by the directory object specified in the
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 for an export job unless the
NOLOGFILE parameter is specified. As with the dump file set, the log file is relative to the server and not the client.
An existing file matching the file name will be overwritten.
To perform a Data Pump Export using Oracle Automatic Storage Management (Oracle ASM), you must specify a
LOGFILE parameter that includes a directory object that does not include the Oracle ASM + notation. That is, the log file must be written to a disk file, and not written into the Oracle ASM storage. Alternatively, you can specify
NOLOGFILE=YES. However, this prevents the writing of the log file.
The following example shows how to specify a log file name if you do not want to use the default:
> expdp hr DIRECTORY=dpump_dir1 DUMPFILE=hr.dmp LOGFILE=hr_export.log
Data Pump Export writes the log file using the database character set. If your client
NLS_LANG environment setting 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.
"Using Directory Objects When Oracle Automatic Storage Management Is Enabled" for information about Oracle Automatic Storage Management and directory objects