Databases Reference
In-Depth Information
Here is some sample output:
Job: SYS_IMPORT_TABLE_04
Operation: IMPORT
Mode: TABLE
State: EXECUTING
Bytes Processed: 0
Current Parallelism: 4
You should see a state of
EXECUTING
, which indicates that the job is actively running. Other items to inspect in the
output are the number of objects and bytes processed. Those numbers should increase as the job progresses.
OS Utilities
You can use the
ps
OS utility to display jobs running on the server. For example, you can search for master and worker
processes, as follows:
$ ps -ef | egrep 'ora_dm|ora_dw' | grep -v egrep
Here is some sample output:
oracle 29871 717 5 08:26:39 ? 11:42 ora_dw01_STAGE
oracle 29848 717 0 08:26:33 ? 0:08 ora_dm00_STAGE
oracle 29979 717 0 08:27:09 ? 0:04 ora_dw02_STAGE
If you run this command multiple times, you should see the processing time (seventh column) increase for one
or more of the current jobs. This is a good indicator that Data Pump is still executing and doing work.
Data Pump Legacy Mode
This feature is covered last in this chapter, but it's quite useful, especially if you're an old-school DBA. As of Oracle
Database 11g Release 2, Data Pump allows you to use the old
exp
and
imp
utility parameters when invoking a Data
Pump job. This is known as legacy mode, and it's a great feature.
You don't have to do anything special to use legacy mode Data Pump. As soon as Data Pump detects a legacy
parameter, it attempts to process the parameter as if it were from the old
exp
/
imp
utilities. You can even mix and
match old legacy parameters with newer parameters; for example,
$ expdp mv_maint/foo consistent=y tables=inv directory=dp_dir
In the output, Data Pump indicates that it has encountered legacy parameters and gives you the syntax for what it
translated the legacy parameter to in Data Pump syntax. For the previous command, here is the output from the Data
Pump session that shows what the
consistent=y
parameter was translated into:
Legacy Mode Parameter: "consistent=TRUE" Location: Command Line,
Replaced with:
"flashback_time=TO_TIMESTAMP('2013-01-25 19:31:54', 'YYYY-MM-DD HH24:MI:SS')"
This feature can be extremely handy, particularly if you're really familiar with the old legacy syntax and wonder
how it's implemented in Data Pump.
