Home » RDBMS Server » Server Administration » Datapumps dumpfile information
Datapumps dumpfile information [message #613229] Thu, 01 May 2014 06:17 Go to next message
altaff
Messages: 16
Registered: January 2014
Location: india
Junior Member
Hi,
Iam having an export dumpfile, I dont know what does it contains,logfile is also removed.
Is there any way to findout the info. about the dumpfile before importing?
Thanks
Re: Datapumps dumpfile information [message #613230 is a reply to message #613229] Thu, 01 May 2014 06:26 Go to previous messageGo to next message
altaff
Messages: 16
Registered: January 2014
Location: india
Junior Member
I hope by mentioning sqlfile parameter in the import command will work.
Re: Datapumps dumpfile information [message #613233 is a reply to message #613230] Thu, 01 May 2014 07:02 Go to previous message
EdStevens
Messages: 985
Registered: September 2013
Senior Member
altaff wrote on Thu, 01 May 2014 06:26
I hope by mentioning sqlfile parameter in the import command will work.


Why "hope"?

http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_import.htm#SUTIL3215


SQLFILE

Default: There is no default

Purpose

Specifies a file into which all of the SQL DDL that Import would have executed, based on other parameters, is written.

Syntax and Description

SQLFILE=[directory_object:]file_name

The 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 hr schema.

For Streams and other Oracle database options, anonymous PL/SQL blocks may appear within the SQLFILE output. They should not be executed directly.

Restrictions

If SQLFILE is specified, then the CONTENT parameter is ignored if it is set to either ALL or DATA_ONLY.

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.

The SQLFILE parameter cannot be used in conjunction with the QUERY parameter.

Example

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 dpump_dir2.
Previous Topic: Block Corruption in Datafile Header
Next Topic: _FILE_SIZE_INCREASE_INCREMENT IN ORACLE 11.2.0.3.0
Goto Forum:
  


Current Time: Sun Oct 21 01:51:50 CDT 2018