Default: There is no default
Syntax and Description
file_name specifies where the import job will write the DDL that would be executed during the job. The SQL is not actually executed, and the target system remains unchanged. The file is written to the directory object specified in the
DIRECTORY parameter, unless another
directory_object is explicitly specified here. Any existing file that has a name matching the one specified with this parameter is overwritten.
Note that passwords are not included in the SQL file. For example, if a
CONNECT statement is part of the DDL that was executed, then it will be replaced by a comment with only the schema name shown. In the following example, the dashes (--) indicate that a comment follows, and the
hr schema name is shown, but not the password.
-- CONNECT hr
Therefore, before you can execute the SQL file, you must edit it by removing the dashes indicating a comment and adding the password for the
For Streams and other Oracle database options, anonymous PL/SQL blocks may appear within the
SQLFILE output. They should not be executed directly.
SQLFILE is specified, then the
CONTENT parameter is ignored if it is set to either
To perform a Data Pump Import to a SQL file using Oracle Automatic Storage Management (Oracle ASM), the
SQLFILE parameter that you specify must include a directory object that does not use the Oracle ASM + notation. That is, the SQL file must be written to a disk file, not into the Oracle ASM storage.
SQLFILE parameter cannot be used in conjunction with the
The following is an example of using the
SQLFILE 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 DIRECTORY=dpump_dir1 DUMPFILE=expfull.dmp SQLFILE=dpump_dir2:expfull.sql
A SQL file named
expfull.sql is written to