Professional Documents
Culture Documents
Data Pump2
Data Pump2
** Data Pump responds back to the client with the traditional utility
** processing messages.
** OK, here is where I hit CONTROL-C to break out of the client session.
** The Data Pump Export continues to run. It displays the prompt below:
Export>
** I typed in EXIT to disconnect from the client session and return to the
** Operating System.
Export> exit
** I created another session to the database and started another Data Pump Expor
t.
** I created a third session and activated SQL*PLUS to select from DBA_DATAPUMP_
JOBS.
** Notice that I still have a client attached to my second Export. The first on
e
** that I broke out of is still running but shows no attached (connected) sessio
ns.
1* select * from dba_datapump_jobs
OWNER JOB_NAME OPERATION JOB_MODE STATE DEGREE ATTACHE
D_SESSIONS DATAPUMP_SESSIONS
----- ------------------------- ---------- ---------- ----------- ------ -------
---------- -----------------
FOOT SYS_EXPORT_FULL_01 EXPORT FULL EXECUTING 1
0 2
FOOT SYS_EXPORT_SCHEMA_01 EXPORT SCHEMA EXECUTING 1
1 3
** I am attaching back to the first Export using the default job name that Oracl
e supplied. I can
** also choose to name the job when I first submit it.
$ expdp foot/foot attach=SYS_EXPORT_FULL_01
** Data Pump responds by giving me a status
** I can also manually enter a STATUS command at any time to see the status of
the job.
** Note that I only have one worker executing.
Export>
Export> status
Job: SYS_EXPORT_FULL_01
Operation: EXPORT
Mode: FULL
State: EXECUTING
Bytes Processed: 0
Current Parallelism: 1
Job Error Count: 0
Dump File: /app/oracle/product/10.2/db/admin/ctitst/dpdump/expfull.dmp
bytes written: 4,096
Worker 1 Status:
State: EXECUTING
Object Schema: SYSMAN
Object Name: MGMT_DB_FEATUREUSAGE
Object Type: DATABASE_EXPORT/SCHEMA/TABLE/TABLE
Completed Objects: 471
Worker Parallelism: 1
Export>
** I can use the PARALLEL command line parameter to dynamically change the job's
number of
** parallel processes.
Export> parallel=2
** Executing another STATUS command to confirm if the job is indeed using parall
el workers.
** We can see two workers are now running and the Current Parallelism indicator
is now 2.
Export> status
Job: SYS_EXPORT_FULL_01
Operation: EXPORT
Mode: FULL
State: EXECUTING
Bytes Processed: 48,674,768
Percent Done: 72
Current Parallelism: 2
Job Error Count: 0
Dump File: /app/oracle/product/10.2/db/admin/ctitst/dpdump/expfull.dmp
bytes written: 54,796,288
Worker 1 Status:
State: EXECUTING
Object Schema: SYSMAN
Object Name: MGMT_HC_HARDWARE_MASTER
Object Type: DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Completed Objects: 55
Total Objects: 626
Worker 2 Status:
State: EXECUTING
Object Schema: SH
Object Name: COSTS
Object Type: DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Completed Objects: 24
Total Objects: 626
** Attempting to attach again. Data Pump can't find the job because it is compl
ete.