Oracle Faq

Hi Friends,

As we know one of the new features of oracle 10g is export ans import datapump which uses inbuild API’s to take export and which is found to be 10% faster and also includes new features which was not available in conventional export and import

For e.g with datapump we can take schema level export with only selected data objects within that schema using datapump ‘INCLUDE’ keyword or we can take entire export of entire schema except few unwanted objects using ‘EXCLUDE’ keyword

Here below are listed the possible options with export dataguard which can be obtained by using following command

expdp -help

Export: Release 10.2.0.1.0 – 64bit Production on Tuesday, 13 February, 2007

16:43:09 Copyright (c) 2003, 2005, Oracle. All rights reserved.

The Data Pump export utility provides a mechanism for transferring data objects between Oracle databases.

The utility is invoked with the following command:

Example: expdp scott/tiger DIRECTORY=dmpdir DUMPFILE=scott.dmp.

You can control how Export runs by entering the ‘expdp’ command followed
by various parameters.

To specify parameters, you use keywords:

Format: expdp KEYWORD=value or KEYWORD=(value1,value2,…,valueN)

Example: expdp scott/tiger DUMPFILE=scott.dmp DIRECTORY=dmpdir SCHEMAS=scott or TABLES=(T1:P1,T1:P2),if T1 is partitioned table

USERID must be the first parameter on the command line.

Description (Default)

ATTACH:Attach to existing job, e.g. ATTACH [=job name].

COMPRESSION:Reduce size of dumpfile contents where valid keyword values are: (METADATA_ONLY) and NONE.

CONTENT:Specifies data to unload where the valid keywords are:(ALL), DATA_ONLY, and METADATA_ONLY.

DIRECTORY: Directory object to be used for dumpfiles and logfiles.

DUMPFILE: List of destination dump files (expdat.dmp), e.g. DUMPFILE=scott1.dmp, scott2.dmp, dmpdir:scott3.dmp.

ENCRYPTION_PASSWORD:Password key for creating encrypted column data.

ESTIMATE:Calculate job estimates where the valid keywords are:(BLOCKS) and STATISTICS.

ESTIMATE_ONLY:Calculate job estimates without performing the export.

EXCLUDE:Exclude specific object types, e.g. EXCLUDE=TABLE:EMP.

FILESIZE:Specify the size of each dumpfile in units of bytes.

FLASHBACK_SCN:SCN used to set session snapshot back to.

FLASHBACK_TIME:Time used to get the SCN closest to the specified time.

FULL:Export entire database (N).

HELP:Display Help messages (N).

INCLUDE:Include specific object types, e.g. INCLUDE=TABLE_DATA.

JOB_NAME:Name of export job to create.

LOGFILE:Log file name (export.log).

NETWORK_LINK:Name of remote database link to the source system.

NOLOGFILE:Do not write logfile (N).

PARALLEL:Change the number of active workers for current job.

PARFILE:Specify parameter file.

QUERY:Predicate clause used to export a subset of a table.

SAMPLE:Percentage of data to be exported;

SCHEMAS:List of schemas to export (login schema).

STATUS: Frequency (secs) job status is to be monitored where the default (0) will show new status when available.

TABLES:Identifies a list of tables to export – one schema only.

TABLESPACES:Identifies a list of tablespaces to export.

TRANSPORT_FULL_CHECK:Verify storage segments of all tables (N).

TRANSPORT_TABLESPACES: List of tablespaces from which metadata will be unloaded.

VERSION: Version of objects to export where valid keywords are:(COMPATIBLE), LATEST, or any valid database version.

The following commands are valid while in interactive mode.Note: abbreviations are allowed

Command

ADD_FILE:Add dumpfile to dumpfile set.

CONTINUE_CLIENT:Return to logging mode. Job will be re-started if idle.

EXIT_CLIENT:Quit client session and leave job running.

FILESIZE:Default filesize (bytes) for subsequent ADD_FILE commands.

HELP:Summarize interactive commands.

KILL_JOB:Detach and delete job.

PARALLEL: Change the number of active workers for current job.PARALLEL=.

START_JOB: Start/resume current job.

STATUS: Frequency (secs) job status is to be monitored where the default (0) will show new status when available.STATUS[=interval]

STOP_JOB:Orderly shutdown of job execution and exits the client.

STOP_JOB=IMMEDIATE performs an immediate shutdown of the Data Pump job.