Oracle 10G Datapump, Part 1:: Jim Czuprynski

Oracle 10g DataPump, Part 1:
Overview
By Jim Czuprynski
Synopsis. Oracle 10g's new DataPump utility is designed as the eventual replacement for
the original Oracle Import and Export utilities. This article - the first in a series - provides an
overview of the DataPump's suite of tools for extracting, transforming, and loading data
within an Oracle database.
Oracle's Import and Export utilities offer a great way to create, retain, and reload a point-intime snapshot of a database's structure and contents at the table, schema, tablespace, or
database level. Database exports also have a place as a potential third line of defense in an
in-depth disaster recovery plan (please view my article on Becoming A Master of Disaster
for a more detailed discussion of this concept).
I have also used these utilities on a regular basis to migrate data from our production
environment to multiple development environments, but as reliable as these utilities are,
they do have some drawbacks that needed to be addressed:
Operations are difficult to restart. If an export session died because it ran out of disk
space, or if the session was terminated deliberately or accidentally, the only option is to
restart the entire export from the beginning, or to create a new export control file at the
point of failure and initiate the export again.
Execution is client-side and single-threaded. The Import and Export utilities use a
client process to execute their respective operations. This means that the most powerful
source of information - the database server itself - is unavailable to help control the Import
or Export operation. Also, there is no way to utilize parallel processing on a database server
while exporting data, so each Export operation is essentially one single, serial, potentially
long-running task.
Dump files can grow enormously. The Export utility creates one or more export dump
files during each session; during a complete dump of a database, these files can obviously
grow quite large. Since it is difficult to estimate the approximate expected size of the
completed export files, the operation may fail due to disk space constraints. Also, to import
just one table or database object from a multi-schema export file, the Import utility has to
read all dump files to locate the object before it can be restored - obviously not an optimal
situation!
Tuning mechanisms are limited. Methods to tune a poorly executing Export or Import
operation are relatively limited and somewhat arcane. Experimenting with different settings
for the BUFFER parameter -- which controls the maximum number of rows fetched into the
Export utility's buffer at one time - is one of the few recommended options for improving
performance.
Progress monitoring is difficult. While a DBA can certainly monitor the command session
that is running the operation, or review the spooled output from an operation, there is no
simple way to tell exactly how efficiently an Export or Import operation is performing, and
there is no simple way to tell exactly what percentage of a large operation is completed.
Database object filtering features are limited. While it is certainly possible to export
and import selected individual tables from a database or schema, filtering features are
relatively limited. For example, it is impossible to export all tables with common names
across schemas within the same export session. It is also impossible to select specific
database object types other than tables (like packages, stored procedures, or triggers) for
inclusion in an export dump file.
Enter The DataPump: Features Overview
Fortunately, Oracle 10g has addressed many of these issues with the DataPump, a new set
of utilities that significantly expands the capabilities of the original Export and Import
utilities.
Server-side parallel execution. DataPump Import and Export operations are scheduled
and processed within the database server itself as a DataPump job - a much more effective
method than client-side execution. In addition, if the database server's OS and hardware
can adequately support it, DataPump export operations can take advantage of parallel
processes to write out multiple data streams simultaneously.
Improved control and restartability of operations. Since the database server controls
the DataPump, a DBA can start an Export or Import operation and then detach from it,
allowing the operation to run to completion without further intervention. The DBA can also
reconnect to the operation from another command-line session, interrogate its current
status and choose to pause the operation if necessary. And if it appears that the operation is
dangerously close to failing - for example, because of insufficient disk space for an export
file - the DBA can even add more disk files "on the fly" without canceling the existing
operation. This provides a level of control at least an order of magnitude more powerful
than the current Export/Import utilities.
Simplified monitoring of operational status. DataPump provides a new STATUS
parameter that shows the status of an ongoing Export or Import operation. When STATUS
is specified at operation startup, Oracle will report the operation's status to the terminal
session of the command-line interface at the specified interval. The DBA can also reattach to
a detached DataPump job, issue a STATUS request, determine how far the operation has
progressed, and then detach from the job again.
Automated performance tuning. Unlike the traditional Export and Import utilities,
DataPump implements self-tuning mechanisms to insure that tables are exported and
imported in the most efficient manner. Gone are the BUFFER, COMMIT, COMPRESS,
CONSISTENT, DIRECT, and RECORDLENGTH parameters.
Improved database object filtering. DataPump implements filtering of the database
objects to capture during an Export operation or include as part of an Import operation with
a new set of mutually-exclusive parameters, INCLUDE and EXCLUDE. These parameters
allow the DBA to specify almost any database object for inclusion or exclusion based on its
object type and object name. This dramatically improves flexibility when exporting and
importing; for example, it is now possible to gather objects with similar names across an
entire database.
Export dump file control enhancements. In prior releases, the DBA could specify more
than one dump file as a destination for an Export session; however, once the session
commenced, no additional files could be specified. DataPump Export improves upon this by
permitting parameterized file names similar to the naming conventions for redo logs and
RMAN backup files.
DataPump Concepts
The DataPump is the next logical progression in a series of improvements that have
appeared during the last few Oracle releases. The two most dramatic upgrades involve the
ability to read data extremely quickly via direct path unloading, and the capability to write
data directly to external tables.
Direct Path Unloads. Prior releases of Oracle had introduced the concept of the direct path
load, which permits the server to bypass SQL parsing of INSERT statements so that data
can be inserted directly and with blinding speed into database tables, providing the tables
met certain conditions. Building on this concept, Oracle 10g adds the capability to perform
direct path unloads of database tables within the same limits that apply for direct path
loads.
Writing To External Tables. Oracle 9i Release 2 introduced the ability to read data from
files stored outside the database as external tables using existing Oracle SQL*Loader access
methods. Oracle 10g expands upon this feature by including a new access method,
ORACLE_DATAPUMP, that allows the server to write directly to an external file.
DataPump Export uses these two enhancements to unload data extremely quickly. Even
better, DataPump needs virtually no assistance in deciding which method is fastest for
exporting data, and is relatively self-tuning. For example, the concept of direct vs.
conventional exports is now meaningless, and several of the tuning parameters (e.g.
BUFFER, RECORDLENGTH) have been deprecated.
The DataPump engine will choose to write to external tables over direct path unload
whenever a table meets any of the following criteria:
The table is part of a cluster.

There is an active trigger on the table.
Fine-grained access control is enabled for the table for INSERTs.
One of the table's columns has a referential integrity constraint.
The table has an LOB column, and that LOB column has a domain index.
The table contains a BFILE column or VARRAY column, and those column(s) have an
embedded, opaque TYPE.
DataPump Components
DataPump consists of three components that work in concert to manage and perform
operations:
Command-Line Interface. Like the original Export (EXP.EXE) and Import (IMP.EXE)
command-line interfaces, the DataPump provides two command-line interfaces,
EXPDP.EXE and IMPDP.EXE, for controlling DataPump Export and Import operations,
respectively.
DataPump also expands the command-line interface's capabilities by providing InteractiveCommand Mode. This mode allows the DBA to start a DataPump operation and then
disconnect from it by simply issuing a CTL+C keystroke. Later, the DBA simply opens
another DataPump session while specifying the operation's job name and then issues the
ATTACH directive to reconnect to the session. The DBA can then issue a series of
commands, from taking a pulse of the operation via the STATUS directive, to adding more
export dump files, or even terminating a long-running operation if desired.
DBMS_METADATA. Introduced in Oracle 9i, this PL/SQL supplied package provides
methods to extract and format metadata - literally, "information about information" - from
an Oracle database. At its core, DBMS_METADATA stores metadata in XML format for
ultimate flexibility in its presentation of that metadata.
DataPump Export uses DBMS_METADATA to gather all metadata about the database
objects being processed then stores that metadata in the Export operation's master table.
DataPump Import uses the corresponding master table to extract information from the
export dump file(s), and then uses DBMS_METADATA to create the DDL statements it
needs to create new database objects as part of the Import operation.
DBMS_DATAPUMP. At the heart of the DataPump is the new DBMS_DATAPUMP PL/SQL
supplied package. This package contains methods for exporting data from and importing
data into any Oracle database. EXPDP and IMPDP are actually making calls to this new
package to perform their respective operations.
What is especially powerful about DBMS_DATAPUMP is that a DBA can also utilize it
directly, either in anonymous PL/SQL blocks or within a stored procedure, stored function, or
package, to create custom DataPump Export and Import jobs. I will demonstrate how to
accomplish this in the final article in this series when we look at some of the other advanced
features of the DataPump.
DataPump Jobs, Master Processes, and the Master Table
DataPump also implements major (and in my opinion, elegant!) improvements to the
execution and management of Export and Import operations. Each DataPump operation
uses a master process to manage and control the export or import session. Each master
process is identified by a unique job name, and DataPump automatically assigns one by
default if one is not specified at execution time.
The master process controls the DataPump operation by invoking at least one worker
process that actually performs the Export or Import. (This is extremely similar to the way
Recovery Manager (RMAN) manages backup, restoration and recovery processing.) If the
DataPump operation has requested additional parallel processes for multiple-threaded
processing, more than one worker process will be created and managed.
The master process also creates a master table as a user table within the user account in
which the DataPump job is invoked. This master table is always named the same as the
DataPump job, and it is used slightly differently depending on the type of DataPump
operation, but it is always created within the same user account that is invoking the
operation.
During an Export operation, the master table is created when the job commences, contains
all target objects for the Export, and is retained until the job finishes successfully, at which
point it is dropped. However, if the job is paused or fails due to error, the Export process
uses the master table to determine what objects still need to be exported and how best to
resume the job. Once the job completes successfully, the master table's contents are written
to the Export file itself for use by an Import process.
On the other hand, an Import operation reads the master table from the Export dump file
and then creates the master table under the appropriate user account. During an Import,
the master process uses the master table to decide which database objects need to be
created and in what order before any data is actually imported.
A Simple DataPump Export Scenario
To demonstrate an example of how easy it is to use DataPump for exporting data, I will
create a dump file containing all database objects stored in the Human Resources (HR)
schema for use in a later DataPump Import operation. (The next article will greatly expand
upon the capabilities of DataPump Export, I assure you!)
Listing 1.1 shows how to create a DIRECTORY database object for storage of all DataPump
dump files. DataPump also uses the DIRECTORY object as a default location for log files and
parameter files.
Listing 1.2 provides a set of queries to display listings of what object types can be
processed with the DataPump, and whether a filter can be applied against the object type at
the database, schema, or table level.
Listing 1.3 shows the DataPump Export command issued, its corresponding parameter file,
and the log file that documents the results of the DataPump Export operation.
A Simple DataPump Import Scenario
Using DataPump to import data is equally simple. To illustrate, I have constructed the
following scenario:
The DataPump Export dump file created in the previous scenario will be used to
import data into a new schema, HR_OLTP, that will eventually become the target of
a new online transaction processing application under development.
The new schema needs all of the tables from the existing HR schema and those
tables' related objects, i.e. referential constraints, indexes, sequences, and triggers.
No other database objects should be loaded to this new schema from the existing HR
schema.
See Listing 1.4 for the SQL to create the new schema, the DataPump Import command
issued, its corresponding parameter file, and the log file that documents the results of the
DataPump Import operation.
Monitoring DataPump Operations

Oracle 10g provides two new views, DBA_DATAPUMP_JOBS and
DBA_DATAPUMP_SESSIONS that allow the DBA to monitor the progress of all DataPump
operations. Listing 1.5 shows two queries that return valuable information about ongoing
DataPump jobs and sessions.
Conclusion
Oracle 10g's new DataPump offers significant improvements over the original commandline-based Export and Import utilities, including multi-threaded processing, improved object
filtering capabilities, and restartability. The next article in this series will dive deeply into
utilizing the DataPump effectively to accomplish some typical (and not so typical!) "realworld" export and import tasks.
References and Additional Reading
While there is no substitute for direct experience, reading the manual is not a bad idea,
either. I have drawn upon the following Oracle 10g documentation for the deeper technical
details of this article:
B10750-01 Oracle Database New Features Guide
/*
||
||
||
||
||
||
||
||
||
||
||
*/
Oracle 10g DataPump - Listing 1

Contains examples of new Oracle 10g DataPump Features.
Author: Jim Czuprynski
Usage Notes:
This script is provided to demonstrate various features of Oracle 10g's
new DataPump and should be carefully proofread before executing it against
any existing Oracle database to insure that no potential damage can occur.
------ Listing 1.1: Setting up a DIRECTORY object for DataPump use.

-Note that the directory folder need not exist for this command
-to succeed, but any subsequent attempt to utilize the
DIRECTORY
-object will fail until the folder is created on the server.
-This should be run from SYSTEM for best results
----DROP DIRECTORY export_dir;
CREATE DIRECTORY export_dir as 'c:\oracle\export_dir';

GRANT READ, WRITE ON DIRECTORY export_dir TO hr, sh;
------ Listing 1.2: Determining what object types can be exported/imported
-and filtering levels available
----COL object_path
FORMAT A25
HEADING 'Object Path Name'
COL comments
FORMAT A50
HEADING 'Object Description'
COL named
FORMAT A3
HEADING 'Nmd|Objs'
TTITLE 'Database-Level Exportable Objects'
SELECT
object_path
,named
,comments
FROM database_export_objects;
TTITLE 'Schema-Level Exportable Objects'
SELECT
object_path
,named
,comments
FROM schema_export_objects;
TTITLE 'Table-Level Exportable Objects'
SELECT
object_path
,named
,comments
FROM table_export_objects;
------ Listing 1.3: A simple DataPump Export operation. Note that if the export
-dump file already exists when this is executed, Oracle will
-return an ORA-39000 error and terminate the operation
----EXPDP hr/hr DUMPFILE=export_dir:hr_schema.dmp
LOGFILE=export_dir:hr_schema.explog
>> DataPump Export command issued:
SET ORACLE_SID=zdcdb
EXPDP system/******** PARFILE=c:\rmancmd\dpe_1.expctl
>> DataPump Export parameters file (dpe_1.expctl):
DIRECTORY=export_dir
SCHEMAS=HR,OE
JOB_NAME=hr_oe_schema
DUMPFILE=export_dir:hr_oe_schemas.dmp
LOGFILE=export_dir:hr_oe_schemas.explog
>> Results of Export Operation:
Export: Release 10.1.0.2.0 - Production on Thursday, 10 March, 2005 17:52
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 Production
With the Partitioning, OLAP and Data Mining options
FLASHBACK automatically enabled to preserve database integrity.
Starting "SYSTEM"."HR_OE_SCHEMA": system/********
parfile=c:\rmancmd\dpe_1.expctl
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 2.562 MB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/TABLE/AUDIT_OBJ
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type
SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/VIEW/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/INDEX/SE_TBL_FBM_INDEX_INDEX/INDEX
SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/SE_TBL_FBM_IND_STATS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/SE_POST_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
. . exported "HR"."LOBSEP"
9.195 KB
1 rows
. . exported "HR"."BIGATFIRST"
277.7 KB
10000 rows
. . exported "HR"."APPLICANTS"
10.46 KB
30 rows
. . exported "HR"."APPLICANTS_1"
11.5 KB
45 rows
. . exported "HR"."APPROLES"
6.078 KB
7 rows
. . exported "HR"."APPS"
5.632 KB
3 rows
. . exported "HR"."COST_CENTERS"
6.328 KB
29 rows
. . exported "HR"."COST_CENTER_ASSIGNMENTS"
6.312 KB
20 rows
. . exported "HR"."COUNTRIES"
6.093 KB
25 rows
. . exported "HR"."DATEMATH"
6.984 KB
1 rows
. . exported "HR"."DEPARTMENTS"
7.101 KB
28 rows
. . exported "HR"."DIVISIONS"
5.335 KB
3 rows
. . exported "HR"."EMPLOYEES"
16.67 KB
118 rows
. . exported "HR"."EMPLOYEE_HIERARCHY"
6.414 KB
5 rows
. . exported "HR"."JOBS"
7.296 KB
27 rows
. . exported "HR"."JOB_HISTORY"
6.765 KB
15 rows
. . exported "HR"."LOCATIONS"
7.710 KB
23 rows
. . exported "HR"."MY_USER_ROLES"
6.453 KB
10 rows
. . exported "HR"."PAYROLL_CHECKS"
7.609 KB
6 rows
. . exported "HR"."PAYROLL_HOURLY"
6.039 KB
3 rows
. . exported "HR"."PAYROLL_SALARIED"
5.687 KB
3 rows
. . exported "HR"."PAYROLL_TRANSACTIONS"
7.195 KB
6 rows
. . exported "HR"."REGIONS"
5.296 KB
4 rows
. . exported "HR"."TIMECLOCK_PUNCHES"
5.718 KB
6 rows
. . exported "HR"."USERS"
5.968 KB
3 rows
. . exported "HR"."USER_ROLES"
6.453 KB
10 rows
. . exported "HR"."IOT_TAB"
0 KB
0 rows
. . exported "HR"."NO_UPDATES"
0 KB
0 rows
. . exported "HR"."PLAN_TABLE"
0 KB
0 rows
Master table "SYSTEM"."HR_OE_SCHEMA" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.HR_OE_SCHEMA is:
C:\ORACLE\EXPORT_DIR\HR_OE_SCHEMAS.DMP
Job "SYSTEM"."HR_OE_SCHEMA" successfully completed at 17:53
------ Listing 1.4: A simple DataPump Import. Note that only database objects from
-the HR schema will be used to populate a new schema (HR_OLTP),
-and all objects other than tables and their dependent objects
-will be excluded from the import
---->> SQL to create new HR_OLTP schema:
DROP USER hr_oltp CASCADE;
CREATE USER hr_oltp
IDENTIFIED BY misdev
DEFAULT TABLESPACE example
TEMPORARY TABLESPACE temp02
QUOTA 50M ON example
PROFILE default;
GRANT CONNECT TO hr_oltp;
GRANT RESOURCE TO hr_oltp;
>> DataPump Import command issued:
IMPDP system/****** PARFILE=export_dir:dpi_1.impctl
>> DataPump Import parameters file (dpi_1.impctl):
JOB_NAME=hr_oltp_import
LOGFILE=export_dir:hr_oltp_import.implog
REMAP_SCHEMA=hr:hr_oltp
STATUS=5
>> Results of Import operation:
Import: Release 10.1.0.2.0 - Production on Thursday, 10 March, 2005 18:02
Master table "SYSTEM"."HR_OLTP_IMPORT" successfully loaded/unloaded
Starting "SYSTEM"."HR_OLTP_IMPORT": system/********
parfile=c:\rmancmd\dpi_1.impctl
. . imported "HR_OLTP"."LOBSEP"
9.195 KB
1 rows
. . imported "HR_OLTP"."BIGATFIRST"
277.7 KB
10000 rows
. . imported "HR_OLTP"."APPLICANTS"
10.46 KB
30 rows
. . imported "HR_OLTP"."APPLICANTS_1"
11.5 KB
45 rows
. . imported "HR_OLTP"."APPROLES"
6.078 KB
7 rows
. . imported "HR_OLTP"."APPS"
5.632 KB
3 rows
. . imported "HR_OLTP"."COST_CENTERS"
6.328 KB
29 rows
. . imported "HR_OLTP"."COST_CENTER_ASSIGNMENTS"
6.312 KB
20 rows
. . imported "HR_OLTP"."COUNTRIES"
6.093 KB
25 rows
. . imported "HR_OLTP"."DATEMATH"
6.984 KB
1 rows
. . imported "HR_OLTP"."DEPARTMENTS"
7.101 KB
28 rows
. . imported "HR_OLTP"."DIVISIONS"
5.335 KB
3 rows
. . imported "HR_OLTP"."EMPLOYEES"
16.67 KB
118 rows
. . imported "HR_OLTP"."EMPLOYEE_HIERARCHY"
6.414 KB
5 rows
. . imported "HR_OLTP"."JOBS"
7.296 KB
27 rows
. . imported "HR_OLTP"."JOB_HISTORY"
6.765 KB
15 rows
. . imported "HR_OLTP"."LOCATIONS"
7.710 KB
23 rows
. . imported "HR_OLTP"."MY_USER_ROLES"
6.453 KB
10 rows
. . imported "HR_OLTP"."PAYROLL_CHECKS"
7.609 KB
6 rows
. . imported "HR_OLTP"."PAYROLL_HOURLY"
6.039 KB
3 rows
. . imported "HR_OLTP"."PAYROLL_SALARIED"
5.687 KB
3 rows
. . imported "HR_OLTP"."PAYROLL_TRANSACTIONS"
7.195 KB
6 rows
. . imported "HR_OLTP"."REGIONS"
5.296 KB
4 rows
. . imported "HR_OLTP"."TIMECLOCK_PUNCHES"
5.718 KB
6 rows
. . imported "HR_OLTP"."USERS"
5.968 KB
3 rows
. . imported "HR_OLTP"."USER_ROLES"
6.453 KB
10 rows
. . imported "HR_OLTP"."IOT_TAB"
0 KB
0 rows
. . imported "HR_OLTP"."NO_UPDATES"
0 KB
0 rows
. . imported "HR_OLTP"."PLAN_TABLE"
0 KB
0 rows
ORA-39082: Object type TRIGGER:"HR_OLTP"."BIN$55fGDdubQL6YVYB0dGS/nw==$1"
created with compilation warnings
ORA-39082: Object type TRIGGER:"HR_OLTP"."SECURE_EMPLOYEES" created with
compilation warnings
ORA-39082: Object type TRIGGER:"HR_OLTP"."TR_BRIU_APPLICANTS" created with

ORA-39082: Object type TRIGGER:"HR_OLTP"."UPDATE_JOB_HISTORY" created with
Job "SYSTEM"."HR_OLTP_IMPORT" completed with 8 error(s) at 18:02
------ Listing 1.5: Querying status of DataPump operations
----TTITLE 'Currently Active DataPump Operations'
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A20
HEADING 'JobName'
COL operation
FORMAT A12
HEADING 'Operation'
COL job_mode
FORMAT A12
HEADING 'JobMode'
COL state
FORMAT A12
HEADING 'State'
COL degree
FORMAT 9999
HEADING 'Degr'
COL attached_sessions
FORMAT 9999
HEADING 'Sess'
SELECT
owner_name
,job_name
,operation
,job_mode
,state
,degree
,attached_sessions
FROM dba_datapump_jobs
;
TTITLE 'Currently Active DataPump Sessions'
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A06
HEADING 'Job'
COL osuser
FORMAT A12
HEADING 'UserID'
SELECT
DPS.owner_name
,DPS.job_name
,S.osuser
FROM
dba_datapump_sessions DPS
,v$session S
WHERE S.saddr = DPS.saddr
;
/*
||
||
||
||
||
||
||
||
||
||
||
*/

Usage Notes:

DIRECTORY
----COL object_path
FORMAT A25
COL comments
FORMAT A50
COL named
FORMAT A3
HEADING 'Nmd|Objs'
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments

SCHEMAS=HR,OE

9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows
******************************************************************************
CREATE USER hr_oltp
PROFILE default;
STATUS=5
9.195 KB
1
277.7 KB
10000
10.46 KB
30
11.5 KB
45
6.078 KB
7
5.632 KB
3
6.328 KB
29
6.312 KB
20
6.093 KB
25
6.984 KB
1
7.101 KB
28
5.335 KB
3
16.67 KB
118
6.414 KB
5
7.296 KB
27
6.765 KB
15
7.710 KB
23
6.453 KB
10
7.609 KB
6
6.039 KB
3
5.687 KB
3
7.195 KB
6
5.296 KB
4
5.718 KB
6
5.968 KB
3
6.453 KB
10
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A20
HEADING 'JobName'
COL operation
FORMAT A12
HEADING 'Operation'
COL job_mode
FORMAT A12
HEADING 'JobMode'
COL state
FORMAT A12
HEADING 'State'
COL degree
FORMAT 9999
HEADING 'Degr'
FORMAT 9999
HEADING 'Sess'
SELECT
owner_name
,job_name
,operation
,job_mode
,state
,degree
,attached_sessions
;
COL owner_name
COL job_name
COL osuser
FORMAT A06
FORMAT A06
FORMAT A12
HEADING 'Owner'
HEADING 'Job'
HEADING 'UserID'
SELECT
DPS.owner_name
,DPS.job_name
,S.osuser
FROM
,v$session S
;
/*
|| Oracle 10g DataPump - Listing 1
||
|| Contains examples of new Oracle 10g DataPump Features.
||
|| Author: Jim Czuprynski
||
||
||
||
||
||
*/
Usage Notes:

DIRECTORY
----COL object_path
FORMAT A25
COL comments
FORMAT A50
COL named
FORMAT A3
HEADING 'Nmd|Objs'
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments

SCHEMAS=HR,OE

9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows
******************************************************************************
CREATE USER hr_oltp
PROFILE default;
STATUS=5
9.195 KB
1
277.7 KB
10000
10.46 KB
30
11.5 KB
45
6.078 KB
7
5.632 KB
3
6.328 KB
29
6.312 KB
20
6.093 KB
25
6.984 KB
1
7.101 KB
28
5.335 KB
3
16.67 KB
118
6.414 KB
5
7.296 KB
27
6.765 KB
15
7.710 KB
23
6.453 KB
10
7.609 KB
6
6.039 KB
3
5.687 KB
3
7.195 KB
6
5.296 KB
4
5.718 KB
6
5.968 KB
3
6.453 KB
10
0 KB
0
0 KB
0
0 KB
0
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows
rows

COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A20
HEADING 'JobName'
COL operation
FORMAT A12
HEADING 'Operation'
COL job_mode
FORMAT A12
HEADING 'JobMode'
COL state
FORMAT A12
HEADING 'State'
COL degree
FORMAT 9999
HEADING 'Degr'
FORMAT 9999
HEADING 'Sess'
SELECT
owner_name
,job_name
,operation
,job_mode
,state
,degree
,attached_sessions
;
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A06
HEADING 'Job'
COL osuser
FORMAT A12
HEADING 'UserID'
SELECT
DPS.owner_name
,DPS.job_name
,S.osuser
FROM
,v$session S
;
/*
||
||
||
||
||
||
||
||
||
||
||

Usage Notes:
*/
DIRECTORY
----COL object_path
FORMAT A25
COL comments
FORMAT A50
COL named
FORMAT A3
HEADING 'Nmd|Objs'
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SCHEMAS=HR,OE
9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows
******************************************************************************
CREATE USER hr_oltp
PROFILE default;
STATUS=5
9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows

COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A20
HEADING 'JobName'
COL operation
FORMAT A12
HEADING 'Operation'
COL job_mode
FORMAT A12
HEADING 'JobMode'
COL state
FORMAT A12
HEADING 'State'
COL degree
FORMAT 9999
HEADING 'Degr'
FORMAT 9999
HEADING 'Sess'
SELECT
owner_name
,job_name
,operation
,job_mode
,state
,degree
,attached_sessions
;
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A06
HEADING 'Job'
COL osuser
FORMAT A12
HEADING 'UserID'
SELECT
DPS.owner_name
,DPS.job_name
,S.osuser
FROM
,v$session S
/*
||
||
||
||
||
||
||
||
||
||
||
*/

Usage Notes:


DIRECTORY
----COL object_path
FORMAT A25
COL comments
FORMAT A50
COL named
FORMAT A3
HEADING 'Nmd|Objs'
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SELECT
object_path
,named
,comments
SCHEMAS=HR,OE
9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows
******************************************************************************
CREATE USER hr_oltp
PROFILE default;
STATUS=5

9.195 KB
1 rows
277.7 KB
10000 rows
10.46 KB
30 rows
11.5 KB
45 rows
6.078 KB
7 rows
5.632 KB
3 rows
6.328 KB
29 rows
6.312 KB
20 rows
6.093 KB
25 rows
6.984 KB
1 rows
7.101 KB
28 rows
5.335 KB
3 rows
16.67 KB
118 rows
6.414 KB
5 rows
7.296 KB
27 rows
6.765 KB
15 rows
7.710 KB
23 rows
6.453 KB
10 rows
7.609 KB
6 rows
6.039 KB
3 rows
5.687 KB
3 rows
7.195 KB
6 rows
5.296 KB
4 rows
5.718 KB
6 rows
5.968 KB
3 rows
6.453 KB
10 rows
0 KB
0 rows
0 KB
0 rows
0 KB
0 rows

COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A20
HEADING 'JobName'
COL operation
FORMAT A12
HEADING 'Operation'
COL job_mode
FORMAT A12
HEADING 'JobMode'
COL state
FORMAT A12
HEADING 'State'
COL degree
FORMAT 9999
HEADING 'Degr'
FORMAT 9999
HEADING 'Sess'
SELECT
owner_name
,job_name
,operation
,job_mode
,state
,degree
,attached_sessions
;
COL owner_name
FORMAT A06
HEADING 'Owner'
COL job_name
FORMAT A06
HEADING 'Job'
COL osuser
FORMAT A12
HEADING 'UserID'
SELECT
DPS.owner_name
,DPS.job_name
,S.osuser
FROM
,v$session S
;

Oracle 10G Datapump, Part 1:: Jim Czuprynski

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle 10G Datapump, Part 1:: Jim Czuprynski

Uploaded by

Copyright:

Available Formats

Oracle 10g DataPump, Part 1:

The table is part of a cluster.

Fine-grained access control is enabled for the table for INSERTs.

One of the table's columns has a referential integrity constraint.

Monitoring DataPump Operations

Oracle 10g DataPump - Listing 1

------ Listing 1.1: Setting up a DIRECTORY object for DataPump use.

CREATE DIRECTORY export_dir as 'c:\oracle\export_dir';

ORA-39082: Object type TRIGGER:"HR_OLTP"."TR_BRIU_APPLICANTS" created with

Oracle 10g DataPump - Listing 1

------ Listing 1.1: Setting up a DIRECTORY object for DataPump use.

-dump file already exists when this is executed, Oracle will

Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY

------ Listing 1.1: Setting up a DIRECTORY object for DataPump use.

>> DataPump Export command issued:

Processing object type SCHEMA_EXPORT/SE_POST_SCHEMA_PROCOBJACT/PROCACT_SCHEMA

Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS

Oracle 10g DataPump - Listing 1

ORA-39082: Object type TRIGGER:"HR_OLTP"."BIN$55fGDdubQL6YVYB0dGS/nw==$1"

Oracle 10g DataPump - Listing 1

------ Listing 1.1: Setting up a DIRECTORY object for DataPump use.

-to succeed, but any subsequent attempt to utilize the

>> Results of Import operation:

ORA-39082: Object type TRIGGER:"HR_OLTP"."SECURE_EMPLOYEES" created with

You might also like